From 655619212e4295430f6f8adc14b77a8e0db216f3 Mon Sep 17 00:00:00 2001
From: Sol Fisher Romanoff <sol@solfisher.com>
Date: Sun, 16 May 2021 10:47:31 +0300
Subject: s/hyphen/em dash/g

---
 git.sr.ht/api.md          | 2 +-
 git.sr.ht/index.md        | 2 +-
 git.sr.ht/installation.md | 8 ++++----
 git.sr.ht/send-email.md   | 4 ++--
 4 files changed, 8 insertions(+), 8 deletions(-)

(limited to 'git.sr.ht')

diff --git a/git.sr.ht/api.md b/git.sr.ht/api.md
index c542054..1313a04 100644
--- a/git.sr.ht/api.md
+++ b/git.sr.ht/api.md
@@ -467,4 +467,4 @@ executing `git push`. Your server has 5 seconds to respond to the HTTP request.
 - Push options (specified via `git push -o <option>`) are interpreted as
   `key=value`, and the map is populated as such. For example, `git push -o
   foo=bar` would result in `{"foo": "bar"}`. Options specified without a value -
-  e.g. `-o foo` - will have their value set to an empty string.
+  e.g. `-o foo` — will have their value set to an empty string.
diff --git a/git.sr.ht/index.md b/git.sr.ht/index.md
index 7aff6fa..07c5b2a 100644
--- a/git.sr.ht/index.md
+++ b/git.sr.ht/index.md
@@ -152,7 +152,7 @@ git tag -a <tag name>
 ```
 
 For example, `git tag -a 2.3.4` to tag version 2.3.4. Your text editor will
-open, and you'll be prompted to *annotate* the tag - fill this in with release
+open, and you'll be prompted to *annotate* the tag — fill this in with release
 notes, a changelog, etc. Consider using
 [`git-shortlog`](https://git-scm.com/docs/git-shortlog) to generate your
 changelog.
diff --git a/git.sr.ht/installation.md b/git.sr.ht/installation.md
index 7e785d9..1e9e298 100644
--- a/git.sr.ht/installation.md
+++ b/git.sr.ht/installation.md
@@ -12,13 +12,13 @@ installation](/installation.md#installing-from-packages).
 
 ## Daemons
 
-- `git.sr.ht` - The web service.
-- `git.sr.ht-api` - The API service.
-- `git.sr.ht-webhooks` - Webhook delivery service.
+- `git.sr.ht` — The web service.
+- `git.sr.ht-api` — The API service.
+- `git.sr.ht-webhooks` — Webhook delivery service.
 
 ## Cronjobs
 
-- `gitsrht-periodic` - Performs various maintenance tasks.
+- `gitsrht-periodic` — Performs various maintenance tasks.
 
 ## Configuration
 
diff --git a/git.sr.ht/send-email.md b/git.sr.ht/send-email.md
index 4fee1e4..febe259 100644
--- a/git.sr.ht/send-email.md
+++ b/git.sr.ht/send-email.md
@@ -14,7 +14,7 @@ https://git-send-email.io
 ## 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 - git records your email with
+contact you. The easiest way is to do nothing — git records your email with
 every commit, so someone with a copy of your git repository can figure out how
 to contact you. You'll probably want to make it a bit easier on them, though.
 
@@ -30,7 +30,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
-- 
cgit