# 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](/how-tos/document-elements/making-comments.md) or [insert an editorial note](/how-tos/document-elements/inserting-editorial-notes.md).

## Examples

### All-caps headings

![](/files/-MaTcOYED00dgCVWY-dB)

Solution: Make the heading/s [Sentence case](/style-guides/laws.africa.md#headings).

### Empty body

![](/files/-MaTckTMpajL6VuJOgkn)

Solution: Remove the 'Schedule' introduction (keyword, heading, and subheading), and make sure the body of the document starts after the `BODY` keyword.

### Empty section

![](/files/-MaTinfKtfyPzE_mfZoK)

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

![](/files/-MaTkCW-q3YF7tcUMlVu)

Solution: Check the section numbers in the original. If that's how they are, [insert an editorial note](/how-tos/document-elements/inserting-editorial-notes.md).

### Other duplicates

![](/files/-MaTlF0pbhafwHIZ4hUX)

Solution: Check the numbers in the original. If that's how they are, [insert an editorial note](/how-tos/document-elements/inserting-editorial-notes.md).

### Numbers don't follow

![](/files/-MaTlXtARCWjbbkOSxzj)

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](/how-tos/document-elements/inserting-editorial-notes.md).

### Only one element

![](/files/-MaTm2M9OYu6g3FIAzoB)

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](/how-tos/document-elements/making-comments.md) ('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)

![](/files/-MaU6gjU8k4Z-ttrYDg_)

Solution: These should usually be changed to (1). If in doubt, make a comment to ask for feedback from a reviewer.

### Broken word

![](/files/-MaTbiDcBsZP5koH2QD-)

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

![](/files/-MaU7NClpD6reZo5b3L7)

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](/how-tos/document-elements/making-comments.md) explaining why it isn't an error.

### Space missing after punctuation

![](/files/-MaU83a8GEwC23KnWuJc)

Solution: Insert the missing space.

If there shouldn't be a space for some reason, [make a comment](/how-tos/document-elements/making-comments.md) explaining why it isn't an error.

### Broken link

![](/files/-MaU8UmUkZVNm0AW4lRs)

Solution: See [Working with links](/how-tos/mark-up/work-with-links.md).

### Image missing attachment

![](/files/-MaUA9zGqd_3dv59h5Dm)

Solution: Make sure the name for the file given in Edit view has a corresponding attachment on the document.

### m2

![](/files/-MaUAVhNLv7mn1m6lRud)

Solution: Superscript the 2: `300m2` → `300m{{^2}}`, or make a comment if it shouldn't be superscripted.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.laws.africa/editors/editor-warnings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.