Top-Level Docs updates

Formatting, added TOCs, spelling.

docs/README.md

@@ -6,11 +6,11 @@
 * The BigBang Helm Chart deploys gitrepository and helmrelease Custom Resources to a Kubernetes Cluster that's running the Flux GitOps Operator, these can be seen using `kubectl get gitrepository,helmrelease -n=bigbang`. Flux then installs the helm charts defined by the Custom Resources into the cluster.
 * The BigBang Helm Chart has a values.yaml file that does 2 main things:
   1. Defines which DevSecOps Platform packages/helm charts will be deployed
-  2. Defines what input parameters will be passed through to the chosen helm charts.
+  1. Defines what input parameters will be passed through to the chosen helm charts.
 * You can see what applications are part of the platform by checking the following resources:
-  * [../Packages.md](../Packages.md) lists the packages and organizes them in categories. 
+  * [../Packages.md](../Packages.md) lists the packages and organizes them in categories.
   * [Release Notes](https://repo1.dso.mil/platform-one/big-bang/bigbang/-/releases) lists the packages and their versions.
-  * For a code based source of truth, you can check [BigBang's default values.yaml](../chart/values.yaml), and `[CTRL] + [F]` "repo:", to quickly iterate through the list of applications supported by the BigBang team. 
+  * For a code based source of truth, you can check [BigBang's default values.yaml](../chart/values.yaml), and `[CTRL] + [F]` "repo:", to quickly iterate through the list of applications supported by the BigBang team.
 
 ## How do I deploy BigBang?
 
@@ -23,7 +23,7 @@ The following is a general overview of the process, the [deployment guides](guid
    * Install Flux GitOps Operator on the Cluster.
    * Configure Flux, the Cluster, and the Git Repo for GitOps Deployments that support deploying encrypted values.
    * Commit to the Git Repo BigBang's values.yaml and encrypted secrets that have been configured to match the desired state of the cluster (including HTTPS Certs and DNS names).  
-2. `kubectl apply --filename bigbang.yaml`
+1. `kubectl apply --filename bigbang.yaml`
    * [bigbang.yaml](https://repo1.dso.mil/platform-one/big-bang/customers/template/-/blob/main/dev/bigbang.yaml) will trigger a chain reaction of GitOps Custom Resources' that will deploy other GitOps CR's that will eventually deploy an instance of a DevSecOps Platform that's declaratively defined in your Git Repo.
    * To be specific, the chain reaction pattern we consider best practice is to have:
      * bigbang.yaml deploys a gitrepository and kustomization Custom Resource