[gov][pcac]: Correcting the document title

doc/common/chapter00.rst

@@ -131,7 +131,7 @@ Architectural Principles
 Following are a number of key architectural principles that apply to all Reference Architectures produced by the Anuket project:
 
 1. **Open-source preference:** for building Cloud Infrastructure
-   solutions, components and tools, using open-source technology.
+   solutions, components, and tools.
 2. **Open APIs:** to enable interoperability, component
    substitution, and minimise integration efforts.
 3. **Separation of concerns:** to promote lifecycle independence of

doc/gov/README.rst

@@ -0,0 +1,14 @@
+==========================================================
+Community Guidelines for Anuket Specifications Development
+==========================================================
+
+Table of contents
+-----------------
+
+.. toctree::
+  :numbered:
+  :maxdepth: 1
+
+  chapters/chapter01
+  chapters/chapter09
+

doc/gov/index.rst

@@ -0,0 +1 @@
+README.rst

doc/ref_arch/kubernetes/chapters/chapter03.rst

@@ -5,15 +5,15 @@ Introduction
 ------------
 
 The Anuket Reference Architecture (RA2) for Kubernetes based cloud infrastructure is intended to be an industry
-standard-independent Kubernetes reference architecture that is not tied to any specific offering or distribution. 
+standard-independent Kubernetes reference architecture that is not tied to any specific offering or distribution.
 No vendor-specific enhancements are required to achieve conformance with the Anuket specifications.
 Conformance to these specifications can be achieved by using upstream components or features that are developed by the
 open source community, and conformance is ensured by successfully running the RC2 conformance testing suite.
 
 By using the Reference Architecture (RA2) for Kubernetes based cloud infrastructure specifications, operators can
 deploy infrastructure that will run any VNF or CNF that has successfully run on an RA2-conformant infrastructure. The
 purpose of this chapter is to outline all the components required to provide Telco-grade Kubernetes in a consistent and
-reliable way. The specification of how to setup these components is detailed in 
+reliable way. The specification of how to setup these components is detailed in
 :ref:`Chapter 04<chapters/chapter04:component level architecture>`.
 
 Kubernetes is already a well-documented and widely deployed open source project of the Cloud Native

doc/ref_arch/kubernetes/chapters/chapter04.rst

@@ -111,7 +111,7 @@ the following specifications:
      - :ref:`RI2 Infrastructure Requirements <ref_impl2:chapters/chapter03:Infrastructure Requirements>`
    * - ra2.ch.011
      - Virtual Node CPU Quantity
-     - If using VMs, the Kubernetes Nodes must be equipped with at least 16 vCPUs. 
+     - If using VMs, the Kubernetes Nodes must be equipped with at least 16 vCPUs.
 
        .. note::
 
@@ -124,7 +124,7 @@ the following specifications:
    * - ra2.ch.012
      - Kubernetes Node RAM Quantity
      - The Kubernetes Nodes must be equipped with at least 32GB of RAM.
-     
+
        .. note::
 
         Note, extra RAM capacity should be provisioned to cater for
@@ -319,7 +319,7 @@ the following specifications:
      -
    * - ra2.k8s.007
      - DevicePlugins Feature Gate
-     - When hosting workloads matching the High Performance profile, the DevicePlugins feature gate must be enabled. 
+     - When hosting workloads matching the High Performance profile, the DevicePlugins feature gate must be enabled.
        --feature-gates="...,DevicePlugins=true,..."
 
        .. note::

doc/ref_arch/kubernetes/chapters/chapter06.rst

@@ -25,7 +25,7 @@ A feature can be in Alpha, Beta or GA stage:
 - Alpha features are disabled by default, may be buggy, and support may be dropped
 - Beta features are disabled by default, are well tested, and support will not be dropped (although breaking API
   changes may happen). Any existing Beta feature as of 1.24 will continue to be enabled by default, but new beta APIs
-  and features will not be enabled by default after Kubernetes 1.24. 
+  and features will not be enabled by default after Kubernetes 1.24.
   More in `KEP-3136 <https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/3136-beta-apis-off-by-default/README.md>`__
 - GA features are stable, always enabled and cannot be disabled.