s/hyphen/em dash/g

2 files changed, 9 insertions, 9 deletions

diff --git a/hg.sr.ht/email.md b/hg.sr.ht/email.md
index 3421d34..af0e658 100644
--- a/hg.sr.ht/email.md
+++ b/hg.sr.ht/email.md
@@ -28,15 +28,15 @@ out, check out the [sr.ht-dev][sr.ht-dev] mailing list.
 [sr.ht-dev]: https://lists.sr.ht/~sircmpwn/sr.ht-dev
 
 Unsure if your setup is correct? Try sending the patch to sir@cmpwn.com for
-feedback first - make sure you mention in the email that you want feedback.
+feedback first — make sure you mention in the email that you want feedback.
 
 # For contributors
 
 ## Preparing your changes
 
-There's no need to "fork" the repository you want to contribute to -- simply use
+There's no need to "fork" the repository you want to contribute to — simply use
 [`hg clone`][hg-clone] to obtain a local copy of the mercurial repository and
-[work normally][work-normally]. Be deliberate about your commits -- use
+[work normally][work-normally]. Be deliberate about your commits — use
 meaningful commit messages and take special care to commit your work in the form
 of logically separate changes. When it comes time to review your work, your
 commit history is an important tool for the reviewer and will be closely
@@ -48,10 +48,10 @@ examined.
 # Find out where to send your changes
 
 This workflow is optional for projects hosted on sr.ht and each project will
-have different requirements - review them carefully. To use this guide, you need
-to find an email address to send your work to - this will often be a mailing
+have different requirements — review them carefully. To use this guide, you need
+to find an email address to send your work to — this will often be a mailing
 list on [lists.sr.ht](/lists.sr.ht). You will also want to find people who can
-help review your changes - look for dedicated maintainers for the modules you're
+help review your changes — look for dedicated maintainers for the modules you're
 working on, or use [`hg annotate`][hg-annotate] to find people who have recently
 worked on similar code.
 
@@ -201,7 +201,7 @@ any other value passed through the command-line.
 ## Tell people how to contribute
 
 The first thing you need to do is help potential contributors figure out how to
-contact you. The easiest way is to do nothing - mercurial records your email
+contact you. The easiest way is to do nothing — mercurial records your email
 with every commit, so someone with a copy of your mercurial repository can
 figure out how to contact you. You'll probably want to make it a bit easier on
 them, though.
@@ -218,7 +218,7 @@ When a patch comes in, you should review it carefully. Read the code, apply the
 patch locally and make sure it compiles, test the changes, and so on. During
 this process you'll probably come up with feedback on the patch. Pull open that
 email client and compose a reply to the patch author. When your client composes
-the reply, don't be afraid to slice and dice the email you're replying to - trim
+the reply, don't be afraid to slice and dice the email you're replying to — trim
 out the fat and only include specific lines that you want to comment on.
 
 If you only have small comments here and there, feel free to make the changes
diff --git a/hg.sr.ht/installation.md b/hg.sr.ht/installation.md
index b2b4177..2da2ac2 100644
--- a/hg.sr.ht/installation.md
+++ b/hg.sr.ht/installation.md
@@ -12,7 +12,7 @@ installation process](/installation.md#installing-from-packages).
 
 ## Daemons
 
-- `hg.sr.ht` - The web service.
+- `hg.sr.ht` — The web service.
 
 ## Cronjobs