git: fae4bec720 - main - FreeBSD Licensing Policy: markup, punctuation

The branch main has been updated by grahamperrin:

URL: https://cgit.FreeBSD.org/doc/commit/?id=fae4bec720c3d641187be76c7a77d5499b4962e7

commit fae4bec720c3d641187be76c7a77d5499b4962e7
Author:     Graham Perrin <grahamperrin@FreeBSD.org>
AuthorDate: 2023-05-13 23:26:12 +0000
Commit:     Graham Perrin <grahamperrin@FreeBSD.org>
CommitDate: 2023-05-13 23:26:12 +0000

    FreeBSD Licensing Policy: markup, punctuation
    
    Partially fix
    https://bugs.freebsd.org/271399
    – make it easier to assess what remains to be changed.
    
    PR:                      271399
---
 documentation/content/en/articles/license-guide/_index.adoc | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/documentation/content/en/articles/license-guide/_index.adoc b/documentation/content/en/articles/license-guide/_index.adoc
index 248e615ea6..e6d91491dc 100644
--- a/documentation/content/en/articles/license-guide/_index.adoc
+++ b/documentation/content/en/articles/license-guide/_index.adoc
@@ -211,11 +211,12 @@ For further information see https://spdx.org/ and the following sections for how
 Entities that contribute fixes and enhancements to the software collection without an explicit license agree to license those changes under the terms that apply to the modified file(s).
 Project policy, in line with industry practice, only includes a copyright notice from significant contributors to the files in the collection.
 
-There are four types of files in the FreeBSD software collection
+There are four types of files in the FreeBSD software collection:
+
 . Files that have only an explicit copyright notice and license.
 . Files that have both an explicit copyright notice and license, and a SPDX-License-Identifier tag.
-. Files that have only a copyright notice and an SPDX-License-Identifier tag, but no explicit license
-. Files that lack any copyright or license at all
+. Files that have only a copyright notice and an SPDX-License-Identifier tag, but no explicit license.
+. Files that lack any copyright or license at all.
 
 === Only Copyright and License
 
@@ -252,7 +253,8 @@ When reading the license text that is detached from a file, a number of consider
 . Any reference to a copyright notice shall refer to the copyright notice constructed from the licensed file, not from any copyright notice in the license text file itself.
 Many SPDX files have sample copyright notices that are understood to be examples only.
 . When names of entities are referred to in the license text, they shall be construed to apply to the list of all copyright holders listed in the copyright notices of the licensed file.
-For example, the BSD-4-clause license contains the phrase "This product includes software developed by the organization". The phrase 'the organization' should be replaced by the copyright holders.
+For example, the BSD-4-clause license contains the phrase "This product includes software developed by the organization".
+The phrase 'the organization' should be replaced by the copyright holders.
 . When the SPDX offers variations of the license, it is understood the license in the [.filename]#LICENSE/# file represents the exact version of the license selected.
 The SPDX standard exists to match families of licenses and these variations help match similar licenses that the SPDX organization believes to be legally identical.