Noissue - Add [paths] documentation and remove trailing spaces

docs/content/settings.md

Index: docs/content/settings.md
===================================================================
--- a/docs/content/settings.md
+++ b/docs/content/settings.md
@@ -2,22 +2,24 @@
 
 The following sections can be defined in `settings.ini`:
 
-* `[general]`: following settings should be listed here:
+* `[general]`: The following settings should be listed here:
   * `defaultlocale`: The fallback locale, to be used whenever no localized
     page/strings can be found for a locale.
-  * `defaultpage`: the default page which is displayed by the server if the URL
+  * `defaultpage`: The default page which is displayed by the server if the URL
     doesn't contain a page name. Note that while the test server will consider
     that setting automatically, the real server might need to be configured
     accordingly.
-  * `crowdin-project-name`: The Crowdin project name, this must be set for if
+  * `crowdin-project-name`: The Crowdin project name, this must be set if
     you intend to use the cms.bin.translate script to update the Crowdin
     translations.
-* `[langnames]`: defines the language names correspoding to particular language
+* `[langnames]`: Defines the language names correspoding to particular language
   codes.
-* `[rtl]`: any language codes listed here are treated as right-to-left languages.
+* `[rtl]`: Any language codes listed here are treated as right-to-left languages.
   The values of the settings are ignored.
-* `[locale_overrides]`: every entry defines that a page should use a different
+* `[locale_overrides]`: Every entry defines that a page should use a different
   locale file, not the one matching its name (to be used when multiple pages
   share localization data).
+* '[paths]': Optionally, this can be used to add additional root folders. E.g.

[Vasily Kuznetsov, 2019/01/10 16:39:46]

I think it would be useful to explain the main use case of this feature:
something like "website inheritance" where we can put parts common to multiple
websites into a separate repository and then reference them from each of the
sharing websites. Let me know if you need help with more details about this or
with drafting the text.

[rhowell, 2019/01/10 20:52:59]

I gave it a shot, but feel free to add or change anything you want!

+  `additional-paths = {}`
 
 Prev: [XTM Integration](../usage/xml-sync.md) | Up: [Home](../../README.md) | Next: [Custom Jinja2 global functions and variables (`globals`)](globals.md)