Adds small edits across pages (#120)

Author: sarahsimpers

snooty.toml

@@ -170,7 +170,7 @@ play-store = "https://play.google.com/store/apps/"
 vault = "`HashiCorp Vault <https://www.vaultproject.io/>`__"
 vpc = ":abbr:`VPC (Virtual Private Cloud)`"
 vnet = "VNet"
-waf = "`Atlas Well-Architected Framework <https://www.mongodb.com/>`__"
+waf = "Atlas Well-Architected Framework"
 wif = "Workforce Identity Federation"
 workload = "Workload Identity Federation"
 

source/auth.txt

@@ -258,7 +258,7 @@ minimize the risk of unauthorized access:
 
 - Follow best practices for
   rotating |api| keys regularly. To learn how to rotate these keys with 
-  {+vault+}, see `the Hashicorp documentation <https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas>`__.
+  {+vault+}, for example, see `the Hashicorp documentation <https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas>`__.
 
 - Use the IP access list for your API keys. To learn more, see
   :atlas:`Require an IP Access List for the {+atlas-admin-api+} </configure-api-access/#optional--require-an-ip-access-list-for-the-atlas-administration-api>`.

source/automation.txt

@@ -1,8 +1,8 @@
 .. _arch-center-automation:
 
-==========
-Automation
-==========
+=====================================
+Automated Infrastructure Provisioning
+=====================================
 
 .. default-domain:: mongodb
 
@@ -62,17 +62,6 @@ programming language or bash script.
 
 To learn more, see :ref:`atlas-admin-api-access`.
 
-GoSDK Client 
-````````````
-
-The {+service+} Go SDK client simplifies interaction with the
-{+atlas-admin-api+} by providing pre-built functions and full |api|
-endpoint coverage. The SDK provides platform-specific and GoLang
-language-specific tools, libraries, and documentation to help build
-applications quickly and easily.  
-
-To learn more, see :ref:`Atlas Go SDK <atlas-admin-sdk>`.
-
 .. _arch-center-iac:
 
 HashiCorp Terraform MongoDB Atlas Provider
@@ -94,6 +83,17 @@ Cluster<arch-center-hierarchy>` examples to get started.
 
 .. include:: /includes/complete-examples.rst
 
+GoSDK Client 
+````````````
+
+The {+service+} Go SDK client simplifies interaction with the
+{+atlas-admin-api+} by providing pre-built functions and full |api|
+endpoint coverage. The SDK provides platform-specific and GoLang
+language-specific tools, libraries, and documentation to help build
+applications quickly and easily.  
+
+To learn more, see :ref:`Atlas Go SDK <atlas-admin-sdk>`.
+
 CloudFormation Resources
 ````````````````````````
 
@@ -148,10 +148,7 @@ the same tooling and pipelines and use the |ak8so| to automate updating
 If you don't already have an existing tool integrated into your
 development workflow, we recommend an :ref:`IaC tool <arch-center-iac>` 
 because they provide more robust options for infrastructure provisioning
-and state management. If you instead call the {+atlas-admin-api+}
-directly or use the GoSDK, which wraps the {+atlas-admin-api+}, you
-might need to recreate your infrastructure provisioning each time to
-match your needs across environments.
+and state management.
 
 You can also use a combination of multiple tools. For example, use IaC
 tool for provisioning and state management, and leverage the

source/hierarchy.txt

@@ -250,7 +250,8 @@ To learn more about parsing billing data using tags, see
 
 In a dedicated deployment ({+cluster+} size ``M10``\+), {+service+}
 allocates resources exclusively. We recommend dedicated deployments
-because they provide high security and performance.
+because they provide higher security and performance than shared
+clusters.
 
 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
@@ -292,7 +293,7 @@ the {+cluster+} resources required by using your organization's approximate data
      - Storage Range: Azure
      - CPUs (#)
      - Default RAM
-     - IOPS
+     - Default IOPS
      - Recommended For
 
    * - Small

source/landing-zone.txt

@@ -48,10 +48,11 @@ pre-configured cloud environment for {+service+} that conforms to your organizat
 move workloads to the cloud, and it is often provisioned
 programmatically using an API or tools like Terraform.
 
-An {+service+} landing zone defines the default and minimum settings
-that teams use to deploy workloads in {+service+}. A landing zone also
-defines the tools and settings that teams should leverage in order to
-integrate systems with {+service+} and their applications connecting to {+service+}.
+An {+service+} landing zone defines the default, minimum, and maximum
+settings that teams use to deploy workloads in {+service+}. A landing
+zone also defines the tools and settings that teams should leverage in
+order to integrate systems with {+service+} and their applications
+connecting to {+service+}.
 
 Why Do You Need a Landing Zone?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -82,13 +83,16 @@ requirements when you create a landing zone:
    * - System Hierarchy Requirements
      - Identify how you will group database {+clusters+} for management
        and isolation. For example, clarify how your team should arrange
-       {+service+} projects or {+service+} organizations. 
+       {+service+} organizations, projects, and {+clusters+}. 
 
        To get recommendations and learn more about this topic, see
        :ref:`arch-center-hierarchy`.
    * - Access Controls
      - Identify MongoDB {+service+} Control Plane access controls, and
-       database access controls for both workload and workforce principals. Create a comprehensive list of principals and mechanisms for how you will authenticate and authorize. Define {+service+} API key access controls, including authorizations and expiration rules.
+       database access controls for both workload and workforce principals. Create a comprehensive list of principals and mechanisms for how you will authenticate and authorize. Define {+service+} API key policies, including authorizations and internal policies for key rotation.
+
+       To get recommendations and learn more about this topic, see
+       :ref:`arch-center-auth`.
    * - Change Control and Auditability Requirements
      - Clarify any change control or audit controls requirements. This
        can include change approval processes and tools, along with

source/network-security.txt

@@ -114,6 +114,26 @@ you must update your connection string to reflect your new cluster topology.
 In the case of adding new shards, the failure to reconnect the application 
 clients may cause your application to suffer from a data outage.
 
+Private Endpoints
+`````````````````
+
+A private endpoint facilitates a one-way connection from your own |vpc|
+to your {+service+} |vpc|, without permitting {+service+} to initiate a
+reciprocal connection. This allows you to make use of secure connections
+to {+service+} without extending your network trust boundary. The following
+private endpoints are available:
+
+- {+aws+} :aws:`PrivateLink </vpc/latest/userguide/endpoint-services-overview.html>`,
+  for connections from {+aws+} |vpc|\s
+- {+azure+} :azure:`Private Link </private-link/private-link-overview>`,
+  for connections from {+azure+} {+vnet+}s
+- :gcp:`Private Service Connect </vpc/docs/private-service-connect>`,
+  for connections from {+gcp+} |vpc|\s
+
+.. figure:: /includes/images/private-link.svg
+   :alt: "An image representing how MongoDB Atlas private endpoints work."
+   :figwidth: 750px
+
 VPC/{+vnet+} Peering
 `````````````````````````````
 
@@ -140,26 +160,6 @@ based on the |cidr| block. For example, a project with a |cidr| block of
    :alt: "An image representing how MongoDB Atlas VPC/VNet peering works."
    :figwidth: 750px
 
-Private Endpoints
-`````````````````
-
-A private endpoint facilitates a one-way connection from your own |vpc|
-to your {+service+} |vpc|, without permitting {+service+} to initiate a
-reciprocal connection. This allows you to make use of secure connections
-to {+service+} without extending your network trust boundary. The following
-private endpoints are available:
-
-- {+aws+} :aws:`PrivateLink </vpc/latest/userguide/endpoint-services-overview.html>`,
-  for connections from {+aws+} |vpc|\s
-- {+azure+} :azure:`Private Link </private-link/private-link-overview>`,
-  for connections from {+azure+} {+vnet+}s
-- :gcp:`Private Service Connect </vpc/docs/private-service-connect>`,
-  for connections from {+gcp+} |vpc|\s
-
-.. figure:: /includes/images/private-link.svg
-   :alt: "An image representing how MongoDB Atlas private endpoints work."
-   :figwidth: 750px
-
 Recommendations for Private Endpoints
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

source/scalability.txt

@@ -44,7 +44,7 @@ Upgrading an {+service+} {+cluster+} to the next available {+service+} tier is a
 {+service+} control plane GUI, the 
 `Atlas Administration API <https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Clusters/operation/upgradeSharedCluster>`__, 
 or through IaC tools, such as the |ak8so|, the |service-terraform|, or the {+atlas-cli+}. See 
-:ref:`Automation <arch-center-automation>` to learn more. Changing an {+service+} tier, either upscaling or 
+:ref:`arch-center-automation` to learn more. Changing an {+service+} tier, either upscaling or 
 downscaling, allows zero downtime. The tier changes in a rolling fashion, which involves electing a secondary 
 member as a replacement, promoting this secondary member to become the new primary, then restoring or replacing 
 the failing member to ensure that the cluster is returned to its target configuration as soon as possible.