# Resolving editor warnings ## Steps 1. Check the Table of Contents on the the left-hand side for warnings. 2. Go to the provision to see where exactly the warning is coming from. 3. Edit the provision to resolve the warning; the warning will no longer be there after you Update. 4. Don't forget to save! :) ## Tips * *Do* fix OCR errors and whitespace errors. * *Don't* fix spelling, grammar, punctuation, or numbering errors; rather [make a comment](https://docs.laws.africa/how-tos/document-elements/making-comments) or [insert an editorial note](https://docs.laws.africa/how-tos/document-elements/inserting-editorial-notes). ## Examples ### All-caps headings ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaTaU3WAMIhnLmdAdD-%2F-MaTcOYED00dgCVWY-dB%2Fimage.png?alt=media\&token=eb8afac0-91ad-47f8-b92b-3c3eec73ac61) Solution: Make the heading/s [Sentence case](https://docs.laws.africa/style-guides/laws.africa#headings). ### Empty body ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaTaU3WAMIhnLmdAdD-%2F-MaTckTMpajL6VuJOgkn%2Fimage.png?alt=media\&token=ada9cb86-7794-48f5-913f-ac28585b286a) Solution: Remove the 'Schedule' introduction (keyword, heading, and subheading), and make sure the body of the document starts after the `BODY` keyword. ### Empty section ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaTe9FSP08ZsHYBlAmm%2F-MaTinfKtfyPzE_mfZoK%2Fimage.png?alt=media\&token=f1ade2c9-8261-4c2a-bf41-266efe1f65e6) 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. ### Duplicate section numbers ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaTk3AKXAyd1ylv3THH%2F-MaTkCW-q3YF7tcUMlVu%2Fimage.png?alt=media\&token=4c19c9dc-6606-4de6-b8ee-33c6d3e860ed) Solution: Check the section numbers in the original. If that's how they are, [insert an editorial note](https://docs.laws.africa/how-tos/document-elements/inserting-editorial-notes). ### Other duplicates ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaTk3AKXAyd1ylv3THH%2F-MaTlF0pbhafwHIZ4hUX%2Fimage.png?alt=media\&token=0703a845-5f2f-4660-88c2-72801c6ac96b) Solution: Check the numbers in the original. If that's how they are, [insert an editorial note](https://docs.laws.africa/how-tos/document-elements/inserting-editorial-notes). ### Numbers don't follow ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaTk3AKXAyd1ylv3THH%2F-MaTlXtARCWjbbkOSxzj%2Fimage.png?alt=media\&token=33787690-335e-41b3-9825-8e59d9df734e) 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](https://docs.laws.africa/how-tos/document-elements/inserting-editorial-notes). ### Only one element ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaTk3AKXAyd1ylv3THH%2F-MaTm2M9OYu6g3FIAzoB%2Fimage.png?alt=media\&token=af57d7ff-120a-4df8-a012-15637a97a5bc) 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](https://docs.laws.africa/how-tos/document-elements/making-comments) ('note: as in original'). * This way, if someone else sees the document and the warning, they'll know you've already checked it. ### (l) or (I) instead of (1) ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaU6RTC367oh_zU5LMt%2F-MaU6gjU8k4Z-ttrYDg_%2Fimage.png?alt=media\&token=39bbed77-46c4-4821-af5d-4ddfd86973f9) Solution: These should usually be changed to (1). If in doubt, make a comment to ask for feedback from a reviewer. ### Broken word ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaTaU3WAMIhnLmdAdD-%2F-MaTbiDcBsZP5koH2QD-%2Fimage.png?alt=media\&token=95aeb267-6724-4bb8-a37d-68a4c91da719) 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. ### Space before punctuation ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaU6RTC367oh_zU5LMt%2F-MaU7NClpD6reZo5b3L7%2Fimage.png?alt=media\&token=9c6ccc11-8875-4f80-bd49-37149f939142) 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](https://docs.laws.africa/how-tos/document-elements/making-comments) explaining why it isn't an error. ### Space missing after punctuation ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaU6RTC367oh_zU5LMt%2F-MaU83a8GEwC23KnWuJc%2Fimage.png?alt=media\&token=47b4fef2-13ff-4a7d-8753-0023d233d382) Solution: Insert the missing space. If there shouldn't be a space for some reason, [make a comment](https://docs.laws.africa/how-tos/document-elements/making-comments) explaining why it isn't an error. ### Broken link ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaU6RTC367oh_zU5LMt%2F-MaU8UmUkZVNm0AW4lRs%2Fimage.png?alt=media\&token=bdf9ed19-a8c2-4eba-ae26-29012e92d1e8) Solution: See [Working with links](https://docs.laws.africa/how-tos/mark-up/work-with-links). ### Image missing attachment ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaU6RTC367oh_zU5LMt%2F-MaUA9zGqd_3dv59h5Dm%2Fimage.png?alt=media\&token=96f6e598-082f-4af6-bc76-249ae704f829) Solution: Make sure the name for the file given in Edit view has a corresponding attachment on the document. ### m2 ![](https://672843079-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoitfV0OP-HrMLMazq_%2F-MaU6RTC367oh_zU5LMt%2F-MaUAVhNLv7mn1m6lRud%2Fimage.png?alt=media\&token=fb63266d-575f-44a1-9916-4e6ee95fc56f) Solution: Superscript the 2: `300m2` → `300m{{^2}}`, or make a comment if it shouldn't be superscripted.