Update docs/FAQ.md, blog/big-bang-2-0.md, blog/dev-bigbang-mil-certificate.md,...

Package Merge Request

Package Changes

Formatting, grammar, punctuation, basic editing, and acronym changes made to: Big Bang README page, Big Bang Contributing page, Understanding Big Bang: FAQ page, Blog: Big Bang 2.0, Blog: Big Bang Mil Domain

Package MR

(Link to Package MR here)

For Issue

Closes (link to issue here)

Upgrade Notices

(Include any relevant notes about upgrades here or write "N/A" if there are none)

blog/big-bang-2-0.md

@@ -24,7 +24,7 @@ Beyond these pain points, there are also changes we are making to enable future
 The default core packages in 1.x releases come with both licensing and closed source concerns, as well as some usability concerns in some cases. Several of the default packages will be changing in 2.0 as a result. These changes are listed in the following:
 * **Runtime Security:** NeuVector will replace Twistlock as the default. NeuVector is opensourced and does not come with a license cost.
 * **Logging:** The Promtail/Loki/Grafana (PLG) stack will become the new default stack, replacing Elasticsearch/Fluentbit/Kibana (EFK). PLG has lower resource costs for users, and does not have a license requirement for core features.
-* **olicy Enforcement:** Kyverno will replace Gatekeeper as the default. Kyverno provides a better user experience for policy writing, and is more directly focused on the Kubernetes experience.
+* **Policy Enforcement:** Kyverno will replace Gatekeeper as the default. Kyverno provides a better user experience for policy writing, and is more directly focused on the Kubernetes experience.
 * **Tracing:** Tempo will replace Jaeger as the default. Jaeger has a dependency on Elasticsearch for persistence, and Tempo is better integrated with the PLG stack to tie traces to specific logs.
 
 These will be *small* breaking changes to user values. If you want to continue to deploy Twistlock, for example, you will need to adjust your values to disable NeuVector and enable Twistlock before upgrading. It's also important to note that we will continue to support the alternative packages in all of these cases, we do not intend to lock users in to a single option.