Resolving editor warnings
Last updated
Last updated
Check the Table of Contents on the the left-hand side for warnings.
Go to the provision to see where exactly the warning is coming from.
Edit the provision to resolve the warning; the warning will no longer be there after you Update.
Don't forget to save! :)
Do fix OCR errors and whitespace errors.
Don't fix spelling, grammar, punctuation, or numbering errors; rather make a comment or insert an editorial note.
Solution: Make the heading/s Sentence case.
Solution: Remove the 'Schedule' introduction (keyword, heading, and subheading), and make sure the body of the document starts after the BODY keyword.
Potential solutions:
Move the content of the section under the heading, if it's a section.
Use the PARA keyword, if it's a numbered paragraph in a Schedule or Annexure.
insert a \ before the number so that it gets treated as normal text, if it's a numbered list in the main body.
Delete the number and heading, if it's in the Arrangement of Sections from the original.
Solution: Check the section numbers in the original. If that's how they are, insert an editorial note.
Solution: Check the numbers in the original. If that's how they are, insert an editorial note.
Solution:
First check that the previous element wasn't sucked into the one before it (in this example, see if subsection (3) is at the end of subsection (2)).
Check the numbers in the original. If that's how they are, insert an editorial note.
Solution:
First check that the subsequent element wasn't sucked into this one (in this example, see if subsection (2) is at the end of subsection (1)).
Check the numbers in the original. If that's how they are, make a comment ('note: as in original').
This way, if someone else sees the document and the warning, they'll know you've already checked it.
Solution: These should usually be changed to (1). If in doubt, make a comment to ask for feedback from a reviewer.
Solution: These should usually be joined into one word ('responsible' in this case). If in doubt, make a comment to ask for feedback from a reviewer.
Solution: Find and remove the space. (You may need to use the 'Search' function in Edit view to find it.)
If there should be a space before punctuation for some reason, make a comment explaining why it isn't an error.
Solution: Insert the missing space.
If there shouldn't be a space for some reason, make a comment explaining why it isn't an error.
Solution: See Working with links.
Solution: Make sure the name for the file given in Edit view has a corresponding attachment on the document.
Solution: Superscript the 2: … be 300m2 and … → … be 300m{{^2}} and …, or make a comment if it shouldn't be superscripted.
