From dc59380f65c48d32122c6f8fa07d6a5b3784acd1 Mon Sep 17 00:00:00 2001 From: Dillonn241 Date: Wed, 27 Dec 2023 11:35:50 -0800 Subject: [PATCH] Grammar errors in Producing an Ebook guide --- www/contribute/producing-an-ebook-step-by-step.php | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/www/contribute/producing-an-ebook-step-by-step.php b/www/contribute/producing-an-ebook-step-by-step.php index be7c86e5..4a1d17b4 100644 --- a/www/contribute/producing-an-ebook-step-by-step.php +++ b/www/contribute/producing-an-ebook-step-by-step.php @@ -554,8 +554,8 @@ proceed to seal up my confession, I bring the life of that unhappy Henry Jekyll

  • Clean and lint

    -

    Before you build the ebook for proofreading, it’s a good idea to check the ebook for some common problems you might have run in to during production.

    -

    First, run se clean one more time to both clean up the source files, and to alert you if there are XHTML parsing errors. Even though we ran se clean before, it’s likely that in the course of production the ebook got in to less-than-perfect markup formatting. Remember you can run se clean as many times as you want—it should always produce the same output.

    +

    Before you build the ebook for proofreading, it’s a good idea to check the ebook for some common problems you might have run into during production.

    +

    First, run se clean one more time to both clean up the source files, and to alert you if there are XHTML parsing errors. Even though we ran se clean before, it’s likely that in the course of production the ebook got into less-than-perfect markup formatting. Remember you can run se clean as many times as you want—it should always produce the same output.

    se clean .

    Now, run se lint. If your ebook has any problems, you’ll see some output listing them. We’re expecting some errors, because we haven’t added a cover or completed the colophon or metadata. You can ignore those errors for now, because we’ll fix them in a later step. But, you do want to correct any fixable errors related to your previous work.

    se lint . @@ -598,7 +598,7 @@ proceed to seal up my confession, I bring the life of that unhappy Henry Jekyll

    There are some things that you don’t have to worry much about when proofreading:

    @@ -683,7 +683,7 @@ proceed to seal up my confession, I bring the life of that unhappy Henry Jekyll

    It’s a good idea to run se typogrify and se clean one more time before running these final checks. Make sure to review the changes with git difftool before accepting them—se typogrify is usually right, but not always!

    Now that our ebook is complete, let’s verify that there are no errors at the S.E. style level:

    se lint . -

    Once se lint completes without errors, we’re ready to confirm that there are no errors at the epub level. We do this by invoking se build with the --check-only flag, which will run epubcheck to verify that our final epub has no errors, but won’t output an ebook files, since we don’t need them right now.

    +

    Once se lint completes without errors, we’re ready to confirm that there are no errors at the epub level. We do this by invoking se build with the --check-only flag, which will run epubcheck to verify that our final epub has no errors, but won’t output ebook files, since we don’t need them right now.

    se build --check-only .

    Once that completes without errors, we’re ready to move on to the final step!