diff --git a/www/contribute/producing-an-ebook-step-by-step.php b/www/contribute/producing-an-ebook-step-by-step.php
index b4a832d1..2d59e9ab 100644
--- a/www/contribute/producing-an-ebook-step-by-step.php
+++ b/www/contribute/producing-an-ebook-step-by-step.php
@@ -381,28 +381,6 @@ proceed to seal up my confession, I bring the life of that unhappy Henry Jekyll
se interactive-replace '(?<![Ee]ach and )([Ee])very one(?!\s+of)' "\1veryone" src/epub/text/*
-
Correct change: | -
-
|
-
Incorrect change: | -
-
|
-
se interactive-replace "\b([Aa])ny thing" "\1nything" src/epub/text/*
- se interactive-replace "([Mm])ean time" "\1eantime" src/epub/text/*
Correct change: | -
-
|
-
Incorrect change: | -
-
|
-
se interactive-replace "([Ee])very thing" "\1verything" src/epub/text/*
- After you’ve reviewed the changes, create an [Editorial]
commit. This commit is important, because it gives purists an avenue to revert modernizing changes to the original text.
Note how we preface this commit with [Editorial]
. Any change you make to the source text that can be considered a modernization or editorial change should be prefaced like this, so that the git
history can be easily searched by people looking to revert changes.