Merge branch '6.0' into create-an-emergency-user

Author: stevepiercy

docs/_static/settings.json

@@ -0,0 +1,5 @@
+{
+  "[markdown]": {
+    "editor.formatOnSave": false
+  }
+}

docs/contributing/documentation/authors.md

@@ -337,16 +337,34 @@ We follow [Microsoft Writing Style Guide](https://learn.microsoft.com/en-us/styl
 Key concepts from that guide include the following.
 
 -   Documentation should be informational, but friendly.
--   Address the reader by using "you" instead of "the user", or by using the collective "we" and "our".
+-   Address the reader by using "you" and "your" instead of "the user" or "the user's".
+-   When giving instructions, use the [imperative](https://learn.microsoft.com/en-us/style-guide/grammar/verbs#mood-of-verbs).
+-   Use the [active voice](https://learn.microsoft.com/en-us/style-guide/grammar/verbs#active-and-passive-voice) whenever possible, avoiding the passive voice.
 -   Headings should be "Sentence cased", not "Title Cased".
 
 The Plone Documentation Team adopted additional guidelines.
 
 -   Use one sentence per line.
     Keep sentences short and understandable.
-    This will greatly improve the editing and maintenance of your documentation.
--   Do not follow the PEP8 maximum line length standard.
-    Documentation is narrative text and images, not Python code.
+
+    Never break a single sentence across multiple lines.
+    Documentation is narrative text and images, not code.
+    Do not follow the PEP8 maximum line length standard.
+    Similarly, never use English semantic line breaks.
+    English semantic rules are difficult to understand and enforce.
+
+    Not following this guidance makes pull request reviews needlessly difficult, often resulting in noisy diffs.
+
+    The reviewer can't give targeted feedback for a single sentence when there are multiple sentences on one line.
+    
+    When a single sentence is broken across multiple lines, the reviewer may not know that they can submit [one suggestion for multiple lines](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-comments-to-a-pull-request).
+    Instead, they either make a comment or a single suggestion leaving the author to manually edit the lines.
+    This in turn deprives you of the easy option to commit the suggestion to the pull request by a single click of a button in the GitHub user interface.
+
+    Following this guidance will greatly improve the editing and maintenance of your documentation.
+
+-   Have the file [`.vscode/settings.json`](/_static/settings.json) in the root of your project to prevent VSCode from reformatting files with the `.md` extension. 
+
 -   Use dashes `-` in filenames and avoid underscores.
 -   Images should be no wider than 740 pixels to fit within the documentation's main view port.
     This avoids scaling and reducing legibility of images.

docs/developer-guide/standardize-python-project-configuration.md

@@ -1,10 +1,10 @@
 ---
 myst:
   html_meta:
-    "description": "Standardize project configuration in Plone with plone/meta"
-    "property=og:description": "Standardize project configuration in Plone with plone/meta"
-    "property=og:title": "Standardize project configuration in Plone with plone/meta"
-    "keywords": "Plone 6, standardize, project, configuration, development, plone/meta"
+    "description": "Standardize project configuration in Plone with plone.meta"
+    "property=og:description": "Standardize project configuration in Plone with plone.meta"
+    "property=og:title": "Standardize project configuration in Plone with plone.meta"
+    "keywords": "Plone 6, standardize, project, configuration, development, plone.meta"
 ---
 
 # Standardize Python project configuration
@@ -19,10 +19,10 @@ It does not cover the following.
 
 Plone consists of hundreds of projects.
 To lessen the effort of configuring a new project in the Plone GitHub organization, and to keep these projects current with latest configuration practices, the Plone community agreed upon a trusted set of configuration items.
-The Plone community manages these configuration items using the [`plone/meta`](https://github.com/plone/meta) project.
+The Plone community manages these configuration items using the [`plone.meta`](https://github.com/plone/meta) project.
 
-You can follow these practices in your own projects, or suggest new or alternative configuration items through the `plone/meta` repository, sharing them with the rest of the Plone community.
+You can follow these practices in your own projects, or suggest new or alternative configuration items through the `plone.meta` repository, sharing them with the rest of the Plone community.
 
 ```{seealso}
 See also [`plone/meta` documentation](https://github.com/plone/meta?tab=readme-ov-file#setup) for setup and usage.
-```
+```