Merge pull request #54412 from bergerhoffer/operator-capitalization-update

Adding difference in Operator capitalization for marketing vs technic…

Author: bergerhoffer

contributing_to_docs/doc_guidelines.adoc

@@ -1829,6 +1829,15 @@ style guidelines. For example:
 - Node Tuning Operator
 - Cluster Version Operator
 
+[NOTE]
+====
+Red Hat Brand and Legal guidance for Operator names will likely differ. For marketing materials, they prefer lowercase names for anything that is not a Red Hat product.
+
+However, the Brand team recognizes that there are different standards for marketing materials versus technical content. For this reason, the title case capitalization for Operator names in technical product documentation and OperatorHub is acceptable.
+
+The "Naming" page by Red Hat Brand on the Source provides an overview of naming slide deck that also confirms this difference.
+====
+
 == Declarative config examples
 
 Many of our procedures provide imperative `oc` commands (which cannot be stored in a Git repo). Due to efforts around improving the experience for GitOps users, we sometimes also want to provide a declarative YAML example that achieves the same configuration. This allows users to store these YAML configurations in a Git repo and follow GitOps practices to configure OpenShift.