From 44eada4d22df4ea48e170205ba9e3a4f151c305e Mon Sep 17 00:00:00 2001
From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com>
Date: Thu, 19 Oct 2023 09:12:30 -0700
Subject: [PATCH] sgit -e 's,\\/,/,g' author/README.md

This is because it was decided quite some time ago that there is not
actually a need to escape the '/' in JSON strings and using our jparse
verifies that files with this form are valid JSON.
---
 author/README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/author/README.md b/author/README.md
index 62f25c2e9..849647eaf 100644
--- a/author/README.md
+++ b/author/README.md
@@ -88,11 +88,11 @@ And there must be the following JSON members:
 
 ```json
 "email" : "user0@example.com",
-"url" : "https:\/\/a.host0.example.com\/index.html",
-"alt_url" : "https:\/\/b.host0.example.com\/index.html",
+"url" : "https://a.host0.example.com/index.html",
+"alt_url" : "https://b.host0.example.com/index.html",
 "deprecated_twitter_handle" : "@something",
 "mastodon" : "@mastodon0@example.com",
-"mastodon_url" : "https:\/\/example.org\/@mastodon0",
+"mastodon_url" : "https://example.org/@mastodon0",
 "github" : "@github0",
 "affiliation" : "an affiliation group",
 ```
@@ -158,11 +158,11 @@ Here is a fictitious author_handle.json example:
     "location_code" : "AU",
     "location_name" : "Australia",
     "email" : "user0@example.com",
-    "url" : "https:\/\/a.host0.example.com\/index.html",
-    "alt_url" : "https:\/\/b.host0.example.com\/index.html",
+    "url" : "https://a.host0.example.com/index.html",
+    "alt_url" : "https://b.host0.example.com/index.html",
     "deprecated_twitter_handle" : "@something",
     "mastodon" : "@mastodon0@example.com",
-    "mastodon_url" : "https:\/\/example.org\/@mastodon0",
+    "mastodon_url" : "https://example.org/@mastodon0",
     "github" : "@github0",
     "affiliation" : "an affiliation group",
     "winning_entry_set" : [