Minor coding policy document fixes.

Ironically make the document formatting more consistent and remove
some trailing whitespace.

Changed "When it Rome.." title since may not have the same meaning in
other languages as it does in English.  Also add table of contents to
this section for linking purposes.

Documentation/development/coding-style-policy.md

@@ -87,7 +87,7 @@ you can still commit:
 
     git commit --no-verify
 
-### Correcting Formatting Errors ## {#correcting-formatting-errors}
+### 1.3.1 Correcting Formatting Errors ### {#correcting-formatting-errors}
 
 There is a Git aliases file that provides the right commands to show and correct
 formatting errors. Add to your repository config by running this command from
@@ -108,6 +108,7 @@ other uses:
 when interactive-rebasing):
     * `check_coding.sh --amend [--diff]`
 
+
 # 2. Naming Conventions # {#naming_conventions}
 Before delving into anything as esoteric as indentation and formatting,
 naming conventions need to be addressed. This section does not attempt
@@ -217,6 +218,7 @@ readability.  This generally means -only- use `auto` where std::lib gets
 overly verbose (such as iterators or `std::make_shared`), or when not using
 `auto` would cause line-wraps that can't otherwise be avoided.
 
+
 # 3. Commenting # {#commenting}
 Comments in KiCad typically fall into two categories: in line code
 comments and Doxygen comments. In line comments have no set formatting
@@ -596,12 +598,11 @@ is exposed in the header file, merely by including that one header
 file.
 
 
-# 7. When in Rome... #
-Anywhere there are multiple acceptable options, follow the formatting 
-elsewhere in the same file.
+# 7. When in Doubt... # {#when_in_doubt}
+When editing existing source code files and there are multiple acceptable
+code formatting options or no formatting is defined, follow the existing
+formatting in the file.
 
-If you encounter a situation that has no guidance, follow the formatting
-elsewhere in the same file.
 
 # 8. I Wrote X Lines of Code Before I Read This Document # {#x_lines}
 It's OK. We all make mistakes. Fortunately, KiCad provides a