[v2] manuals: standards.md5: add standard for project names

diff --git a/documentation/0001-manuals-standards.md5-add-standard-for-project-names.patch b/documentation/0001-manuals-standards.md5-add-standard-for-project-names.patch
new file mode 100644
index 0000000000..8b9e36dda6
--- /dev/null
+++ b/documentation/0001-manuals-standards.md5-add-standard-for-project-names.patch
@@ -0,0 +1,70 @@ 
+From 10924847c19a69a8f7fd2acd97f84987cdfea2c8 Mon Sep 17 00:00:00 2001
+From: Michael Opdenacker <michael.opdenacker@bootlin.com>
+Date: Mon, 15 Apr 2024 11:58:54 +0200
+Subject: [RFC][PATCH] manuals: standards.md5: add standard for project names
+
+Set a new standard to introduce project names with single quotes,
+so that they appear in generated text with an italic font,
+to make them easier to distinguish from command names and from
+ordinary English words.
+
+Rework and move the standard for command and file names
+to make the whole description "flow" better.
+
+Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
+CC: Quentin Schulz <quentin.schulz@theobroma-systems.com>
+---
+ documentation/standards.md | 31 ++++++++++++++++---------------
+ 1 file changed, 16 insertions(+), 15 deletions(-)
+
+diff --git a/documentation/standards.md b/documentation/standards.md
+index e0c0cba83c..05c5afffe8 100644
+--- a/documentation/standards.md
++++ b/documentation/standards.md
+@@ -70,27 +70,28 @@ cannot be split without infringing syntactic rules
+ or reducing readability, as well as for command output
+ which should be kept unmodified.
+ 
+-### Project names
++### File, tool and command names
+ 
+-Project names should be capitalized in the same
+-way they are on Wikipedia, in particular:
++File, tool, command and package names should be double tick-quoted.
++For example, ``` ``conf/local.conf`` ``` is preferred over
++`"conf/local.conf"`.
+ 
+-* BitBake
+-* OpenEmbedded
++### Project names
+ 
+-There are exceptions in which such names can be used
+-in lower case:
++Project names should be introduced with single quotes, to have them rendered
++with an italic font and make them easier to distinguish from command names
++(double tick-quoted) and from regular English words.
+ 
+-* When referring to a package name
+-* When referring to the corresponding command name
+-* When used in a cross-reference title. Such
+-  titles are usually in lower case.
++They should also be capitalized in the same way they are on Wikipedia, or on
++their own project pages if they are not described on Wikipedia.
+ 
+-### File, tool and command names
++For example:
+ 
+-File, tool and command names should be double tick-quoted.
+-For example, ``` ``conf/local.conf`` ``` is preferred over
+-`"conf/local.conf"`.
++* ``` `BitBake` ```
++* ``` `ftrace` ```
++
++An exception is when such names are used in a section title, or in a cross-reference
++to a section. In that case, capitalization and quotes are ignored by Sphinx.
+ 
+ ### Variables
+ 
+-- 
+2.34.1
+
diff --git a/documentation/standards.md b/documentation/standards.md
index e0c0cba83c..3fc5796301 100644
--- a/documentation/standards.md
+++ b/documentation/standards.md
@@ -70,27 +70,30 @@  cannot be split without infringing syntactic rules
 or reducing readability, as well as for command output
 which should be kept unmodified.
 
-### Project names
+### File, tool and command names
 
-Project names should be capitalized in the same
-way they are on Wikipedia, in particular:
+File, tool, command and package names should be double tick-quoted.
+For example, ``` ``conf/local.conf`` ``` is preferred over
+`"conf/local.conf"`.
 
-* BitBake
-* OpenEmbedded
+### Project names
 
-There are exceptions in which such names can be used
-in lower case:
+Project names should be introduced with single quotes, to have them rendered
+with an italic font and make them easier to distinguish from command names
+(double tick-quoted) and from regular English words.
 
-* When referring to a package name
-* When referring to the corresponding command name
-* When used in a cross-reference title. Such
-  titles are usually in lower case.
+They should also be capitalized (or not) in the same way they are on Wikipedia,
+or on their own project pages if they are not described on Wikipedia. If a
+project name isn't capitalized, it should remain so even at the beginning of a
+sentence.
 
-### File, tool and command names
+For example:
 
-File, tool and command names should be double tick-quoted.
-For example, ``` ``conf/local.conf`` ``` is preferred over
-`"conf/local.conf"`.
+* ``` `BitBake` ```
+* ``` `ftrace` ```
+
+An exception is when such names are used in a section title, or in a cross-reference
+to a section. In that case, capitalization and quotes are ignored by Sphinx.
 
 ### Variables