Adds more guidance missed from Orgs page (#27)

Author: sarahsimpers

snooty.toml

@@ -47,6 +47,7 @@ azure = "Microsoft Azure"
 az-bs = "Azure Blob Storage"
 az-pl = "Azure Private Link"
 bcp = "Backup Compliance Policy"
+BU = ":abbr:`BU (Business Unit)`"
 c2c-version = "6.0.13"
 c2c-version-7 = "7.0.8"
 mdb-tools-version = "100.10.0"

source/hierarchy.txt

@@ -50,7 +50,7 @@ security settings and governance for your {+service+} enterprise estate:
    * - Organization
      - Invoicing aggregates and generates at the organization level.
        Line items go to cluster level and below. An organization often
-       maps to a business unit (BU) or application.
+       maps to a {+BU+} or application.
 
    * - Project
      - Security configuration for the data plane (including database
@@ -69,6 +69,44 @@ security settings and governance for your {+service+} enterprise estate:
 Recommendations
 ~~~~~~~~~~~~~~~
 
+Development, Testing, Staging, and Production Environments
+``````````````````````````````````````````````````````````
+
+We recommend that you use the following four environments to isolate
+your sandbox and test projects and {+clusters+} from your application
+projects and {+clusters+}:
+
+.. list-table::
+   :header-rows: 1
+   :widths: 15 85
+
+   * - Environment
+     - Description
+
+   * - Development (Dev)
+     - Allow developers to freely try new things in a safe sandbox
+       environment.
+
+   * - Testing (Test)
+     - Test specific components or functions created in the dev
+       environment.
+     
+   * - Staging
+     - Stage all components and
+       functions together to make sure the entire application works 
+       as expected before deploying to production. Staging is similar to
+       the test environment, but ensures that new components work well 
+       with existing components.
+    
+   * - Production (Prod)
+     - The back end for your application that is live for your
+       end users.
+
+For your dev and test environments, you can develop {+service+}
+{+clusters+} locally with the {+atlas-cli+}. To learn more, see 
+:atlascli:`Create a Local {+service+} Deployment
+<atlas-cli-deploy-local>`.
+
 Org and Project Hierarchies
 ````````````````````````````
 
@@ -78,7 +116,7 @@ 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. 
+This hierarchy, which creates fewer |service| organizations, might be useful if you have common teams and permissions across the {+BU+}, and less than the raiseable limit of 250 projects per organization. 
 
 **DIAGRAM TO REPLACE TEXT**
 
@@ -93,7 +131,7 @@ This hierarchy, which creates fewer |service| organizations, might be useful if
     - Project: Product Mgmt App - Test 
     - Project: Product Mgmt App - Dev 
 
-  - Atlas Org: Corporate Products BU
+  - Atlas Org: Corporate Products {+BU+}
 
 .. _project-hierarchy-2:
 
@@ -103,7 +141,7 @@ Recommended Hierarchy 2: More Atlas Organizations
 Consider the following hierarchy for a different enterprise.
 This hierarchy creates a relatively large number of |service|
 organizations: one per application or scrum team. This hierarchy might
-be useful if each of your teams is fairly independent, they don't share people or permissions within a business unit, or they want to buy credits themselves through the cloud provider marketplace. There is
+be useful if each of your teams is fairly independent, they don't share people or permissions within a {+BU+}, or they want to buy credits themselves through the cloud provider marketplace. There is
 no paying organization in this hierarchy.
 
 **DIAGRAM TO REPLACE TEXT**
@@ -147,6 +185,22 @@ sub-organizations' databases.
 
 DIAGRAM
 
+{+Cluster+} Tagging
+```````````````````
+
+We recommend that you tag {+clusters+} with the following details to
+enable easy data parsing for reports:
+
+- {+BU+}
+- Team name
+- Application name
+- Environment
+- Version
+- Email contact
+
+To learn more about parsing billing data using tags, see
+:ref:`arch-center-billing-data`.
+
 .. _arch-center-cluster-size-guide:
 
 {+service+} {+Cluster+} Size Guide
@@ -268,7 +322,7 @@ These examples also apply other recommended configurations, including:
       Create the Organizations
       ~~~~~~~~~~~~~~~~~~~~~~~~
 
-      Run the following command for each business unit. Change
+      Run the following command for each {+BU+}. Change
       the IDs and names to use your actual values:
 
       .. code-block::