Reframes best practices as recommendations for headings (#22)

Author: sarahsimpers

source/automation.txt

@@ -28,8 +28,8 @@ deployments. These tools offer you the flexibility to work with
 |service| through direct scripting, a Kubernetes-native workflow, or
 using Infrastructure as Code (IaC) resources.    
 
-{+service+} Features and Best Practices for Automation
-------------------------------------------------------
+{+service+} Features for Automation
+-----------------------------------
 
 You can automate the management, provisioning, and configuration of
 |service| building blocks like database users and roles, |service|

source/hierarchy.txt

@@ -9,7 +9,7 @@
 .. contents:: On this page
    :local:
    :backlinks: none
-   :depth: 1
+   :depth: 2
    :class: onecol
 
 Organizations, projects, and {+clusters+} are the building blocks
@@ -26,8 +26,11 @@ size for your organizations, projects, and {+clusters+}. This guidance
 helps you optimize your security and performance from the start while
 aligning with your enterprise's billing and access needs.
 
-{+service+} Features and Best Practices for Hierarchy
------------------------------------------------------
+{+service+} Features and Recommendations for Hierarchy
+------------------------------------------------------
+
+Features
+~~~~~~~~
 
 You can use the following levels of hierarchy to define
 security settings and governance for your {+service+} enterprise estate:
@@ -63,13 +66,16 @@ security settings and governance for your {+service+} enterprise estate:
 
 **DIAGRAM**
 
-Suggested Org and Project Hierarchies
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Recommendations
+~~~~~~~~~~~~~~~
+
+Org and Project Hierarchies
+````````````````````````````
 
 .. _project-hierarchy-1:
 
-Suggested Hierarchy 1: Fewer Atlas Organizations
-````````````````````````````````````````````````
+Recommended Hierarchy 1: Fewer Atlas Organizations
+##################################################
 
 Consider the following hierarchy for an example enterprise.
 This hierarchy, which creates fewer |service| organizations, might be useful if you have common teams and permissions across the business unit, and less than the raiseable limit of 250 projects per organization. 
@@ -91,8 +97,8 @@ This hierarchy, which creates fewer |service| organizations, might be useful if
 
 .. _project-hierarchy-2:
 
-Suggested Hierarchy 2: More Atlas Organizations
-```````````````````````````````````````````````
+Recommended Hierarchy 2: More Atlas Organizations
+#################################################
 
 Consider the following hierarchy for a different enterprise.
 This hierarchy creates a relatively large number of |service|
@@ -116,8 +122,8 @@ no paying organization in this hierarchy.
 
 .. _deployment-hierarchy:
 
-Suggested Deployment Hierarchy
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+{+Cluster+} Hierarchy
+`````````````````````
 
 To allow fine-grained access control, we recommend one deployment
 per |service| project.
@@ -144,9 +150,11 @@ DIAGRAM
 .. _arch-center-cluster-size-guide:
 
 {+service+} {+Cluster+} Size Guide
-----------------------------------
+``````````````````````````````````
 
-Use the following {+cluster+} size guide to select a {+cluster+} tier that ensures performance without over-provisioning.
+Use the following {+cluster+} size guide to select a {+cluster+} tier that ensures performance without over-provisioning. The {+cluster+} size guide also provides recommendations on which {+cluster+} tiers
+are suitable for development and testing environments, and which are
+suitable for staging and production environments.
 
 The {+cluster+}
 size guide uses "t-shirt sizing," a common analogy used in software
@@ -290,8 +298,8 @@ These examples also apply other recommended configurations, including:
 
       - :ref:`atlas-projects-list`
 
-      Create One Deployment Per Project
-      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+      Create One {+Cluster+} Per Project
+      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
       .. tabs::
 

source/includes/examples/cli-example-create-clusters-devtest.rst

@@ -5,7 +5,7 @@
      --projectId 56fd11f25f23b33ef4c2a331 \
      --region EASTERN_US \
      --members 3 \
-     --tier M30 \
+     --tier M10 \
      --provider GCP \
      --mdbVersion 8.0 \
      --diskSizeGB 30 \

source/includes/examples/tf-example-tfvars-devtest.rst

@@ -4,7 +4,7 @@
    atlas_org_id = "32b6e34b3d91647abb20e7b8"
    atlas_project_name = "Customer Portal - Dev"
    environment = "dev"
-   cluster_instance_size_name = "M30"
+   cluster_instance_size_name = "M10"
    cloud_provider = "AWS"
    atlas_region = "US_WEST_2"
    mongodb_version = "8.0"

source/includes/shared-settings-clusters-devtest.rst

@@ -1,5 +1,5 @@
 - Backup disabled to conserve costs.
-- Cluster tier set to ``M30`` for a medium-sized application. Use the
+- Cluster tier set to ``M10`` for a dev/test environment. Use the
   :ref:`cluster size guide <arch-center-cluster-size-guide>` to learn
   the recommended cluster tier for your application size.
 

source/index.txt

@@ -20,6 +20,7 @@ The {+atlas-arch-center+}'s content aligns with the {+waf+} pillars:
    :width: 500px
    :align: center
 
+|
 
 - **Operational Efficiency**: Automation, monitoring, and observability
   that enhance efficiency.