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,27 @@
 
 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]': A root folder of another website may be specified here, which will

[Vasily Kuznetsov, 2019/01/14 14:04:31]

I think it would be easier to read if separate the section description and key
description, even though there's only one key. Also I think mentioning "remote
resources" and "repositories" could be confusing so I tried to rewrite it only
mentioning websites and directories (it seems that we use "directory" instead of
"folder" in the rest of the docs, so I tried to be consistent):

* `[paths]`: Configure where things are located on the filesystem:
  * `additional-paths`: One or more additional website root directories (paths
should be relative to the root directory of this website). Pages, templates,
translations, etc. from those websites will be added to this one. This is useful
for sharing common resources between multiple websites.

Feel free to correct further if something sounds odd or unclear.

[rhowell, 2019/01/14 15:11:29]

Yeah, this layout seems to be more clear. Thanks!

+  allow this website to access the remote resources. This is useful for
+  websites that share common resources. If the shared resources are in a
+  separate repository, they can be 'inherited' here by using the key:
+  `additional-paths = {}`
 
 Prev: [XTM Integration](../usage/xml-sync.md) | Up: [Home](../../README.md) | Next: [Custom Jinja2 global functions and variables (`globals`)](globals.md)