From 158e48fa1fc28dfaf3935ddf1d82ace4951dacc9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Grandjean?= Date: Thu, 19 Aug 2021 00:59:19 -0500 Subject: [PATCH] Fix typo --- .../how-to-review-an-ebook-production-for-publication.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/www/contribute/how-tos/how-to-review-an-ebook-production-for-publication.php b/www/contribute/how-tos/how-to-review-an-ebook-production-for-publication.php index fde11d0b..5d2d5b50 100644 --- a/www/contribute/how-tos/how-to-review-an-ebook-production-for-publication.php +++ b/www/contribute/how-tos/how-to-review-an-ebook-production-for-publication.php @@ -16,7 +16,7 @@ require_once('Core.php');

Run se modernize-spelling . at the root of the project directory. Note that this tool may not catch all archaic words. Prudent use of text editor spellcheckers can help picking up some of these. When in doubt, refer to the appropriate authority of spelling as noted in the Manual. Many words that are hyphenated in the past (e.g. to-morrow) are in modern times concatenated. However, these hyphens should all be retained in poetry . That said, obvious sound-alike spelling modernization should be made and accepted.

  • -

    Semanitcate

    +

    Semanticate

    Run se semanticate . at the root of the project directory. Unlike se typogrify or se modernize-spelling, se semanticate is more prone to error or false positives. Judicious use of the git diff command listed in Step 1 would be needed to prevent and revert any unwanted changes.