CommunitySpecification · jorydotcom · Jun 15, 2025 · Feb 24, 2026
diff --git a/.0_CS_Contributor_License_Agreement.md → 00-contributor-license-agreement.md b/.0_CS_Contributor_License_Agreement.md → 00-contributor-license-agreement.md
diff --git a/1._Community_Specification_License-v1.md → 01-community-specification-license-v1.md b/1._Community_Specification_License-v1.md → 01-community-specification-license-v1.md
diff --git a/2._Scope.md → 02-scope.md b/2._Scope.md → 02-scope.md
diff --git a/3._Notices.md → 03-notices.md b/3._Notices.md → 03-notices.md
diff --git a/4._License.md → 04-license.md b/4._License.md → 04-license.md
diff --git a/5._Governance.md → 05-governance.md b/5._Governance.md → 05-governance.md
diff --git a/6._Contributing.md → 06-contributing.md b/6._Contributing.md → 06-contributing.md
diff --git a/7._CS_Template.md → 07-spec-template.md b/7._CS_Template.md → 07-spec-template.md
@@ -8,12 +8,12 @@ A model manuscript of a draft International Standard (known as “The Rice Model
 
 In addition, we recommend using the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" as described in RFC 2119 - https://tools.ietf.org/html/rfc2119
 
-
+ 
 ## Title
 ### Version _______
 ### Status (Pre-draft, Draft, Approved)
 
-
+ 
 © _________________
 
 This specification is subject to the Community Specification License 1.0, available at [https://github.com/CommunitySpecification/1.0](https://github.com/CommunitySpecification/1.0).
@@ -42,7 +42,7 @@ Introduction	i
 
 6	Clause title	1
 
-Annex A (informative)
+Annex A (informative)  
 
 Bibliography	1
 
@@ -68,7 +68,7 @@ THESE MATERIALS ARE PROVIDED “AS IS.” The Contributors and Licensees express
 Introduction
 Type text.
 
-
+ 
 ## Title (Introductory element — Main element — Part : Part title)
 
 1	Scope (mandatory)
@@ -135,7 +135,7 @@ term
 
 text of the definition
 
-4	Clause title
+4	Clause title 
 
 Type text.
 
@@ -145,9 +145,9 @@ Type text.
 
 Use subclauses if required e.g. 5.1 or 5.1.1. For example:
 
-5.1	Subclause
+5.1	Subclause 
 
-5.1.1	Subclause
+5.1.1	Subclause 
 
 6	Clause title
 

diff --git a/8._Code_of_Conduct.md → 08-code-of-conduct.md b/8._Code_of_Conduct.md → 08-code-of-conduct.md
diff --git a/Readme.md b/Readme.md
@@ -10,7 +10,7 @@ The Community Specification allows you to start a specification development effo
 
 ## How to get started?
 
-Instructions for using the Community Specification are included in the ..Getting Started.md file.
+Instructions for using the Community Specification are included in the getting-started.md file.
 
 ## Could I just use an open source license for my specifications? Why should I use a specification license?
 

diff --git a/..Getting Started.md → getting-started.md b/..Getting Started.md → getting-started.md