DOCSP-49282 -- Update Network Security section (#181)

* (DOCSP-47816) [Atlas Architecture] Make follow-up edits from the Automation, Monitoring, and High Availability pages (#125)

* (DOCSP-47816) Emphasizing enterprise benefits and standardizing source constants.

* (DOCSP-47816) Add sample metrics dashboard screenshot.

* (DOCSP-47816) Resize figure.

* (DOCSP-47816) Edit introduction to metrics screenshot.

* (DOCSP-477815) Monitoring and Alerts Edits.

* (DOCSP-47816) Fixing link error.

* (DOCSP-47816) Edits.

* (DOCSP-47816) Standardize heading level.

* (DOCSP-477816) Add maintenance window and failover recommendations.

* (DOCSP-47816) Introduce benefits.

* (DOCSP-47816) Fix broken link.

* (DOCSP-47816) Add link and punctuation to monitoring table.

* (DOCSP-47816) Edits.

* (DOCSP-47816) Simplify distribute data section.

* (DOCSP-47816) Edits.

* (DOCSP-47816) Move test failover to Replica Set Members.

* (DOCSP-47816) Edits for clarity.

* (DOCSP-47816) Simplify introduction.

* (DOCSP-47816) Split complicated intro sentence.

* (DOCSP-47816) Chris Shum review changes.

* (DOCSP-47816) Chris Shum review edits, replacing 2-1-1 diagram with 2-2-1.

* (DOCSP-47820) [Atlas Architecture] Make follow-up edits from the Orgs, Projects, and Clusters page (#129)

* (DOCSP-47820) Atlas CLI Docker addition.

* (DOCSP-47820) Docker edits.

* (DOCSP-47820) Add Multiple Clusters Per Project Section.

* (DOCSP-47820) Add average workload table and example.

* (DOCSP-47820) Combine tables and rework example.

* (DOCSP-47820) Combine tables and rework example.

* (DOCSP-47820) Edits.

* (DOCSP-47820) Edits.

* (DOCSP-47820) Revert footnote.

* (DOCSP-47820) @JuliaMongo review changes.

* (DOCSP-47820) Clarify 'peak' IOPS

* (DOCSP-47820) Chris Shum review changes, remove example IOPS numbers and reference  multiple clusters section.

* (DOCSP-47820) Plural fix.

* (DOCSP-47820) Review change.

* (DOCSP-48480) Adds release notes for March 17 2025 release (#135)

* DOCSP 48498 (#144)

* (DOCSP-47913) Fixes card bugs on Security page (#121) (#122)

* Release (#127)

* (DOCSP-47913) Fixes card bugs on Security page (#121)

* (DOCSP-47879) SEO improvements (#126)

* (DOCSP-47879) SEO improvements

* Changes Features and Recommendations to Guidance for pages that have both

* Lengthens pillar page titles

* (DOCSP-48128) Replaces landing image with shorter version (#130) (#131)

* (DOCSP-48128) Replaces landing image with shorter version

* Tries smaller width

* (DOCSP-48498) Typo fix.

---------

Co-authored-by: Sarah Simpers <[email protected]>

* DOCSP-48791: typo fix

* (DOCSP-48693) Fixes 404s in the Arch Center docs (#150)

* DOCSP-49282 -- Update Network Security section

* DOCSP-49282 -- Network details added

* Apply suggestions from code review

Co-authored-by: kanchana-mongodb <[email protected]>

---------

Co-authored-by: Elyse Foreman <[email protected]>
Co-authored-by: Sarah Simpers <[email protected]>
Co-authored-by: lmkerbey-mdb <[email protected]>
Co-authored-by: John Williams <[email protected]>
Co-authored-by: John Williams <[email protected]>
Co-authored-by: kanchana-mongodb <[email protected]>

Author: 6 people

source/automation.txt

@@ -39,6 +39,7 @@ We recommend that our enterprise customers use {+iac+} tools for the following b
 - **Improved Change Management**: {+iac+} tools support reviews and standardization of infrastructure,
   allowing for better change management practices and compliance. 
 
+
 Features for |service| Automation
 ---------------------------------
 

source/hierarchy.txt

@@ -246,7 +246,7 @@ the same team is responsible for multiple applications across environments.
 This eases the setup cost for features such as private endpoints and customer-managed keys, 
 because all {+clusters+} in the same project share the same project configuration.
 
-However, this {+cluster+} hierarchy might violate the principle of least privilege.
+However, this {+cluster+} hierarchy may violate the principle of least privilege.
 
 Deploy multiple {+clusters+} within the same project only if both of the following are true:
 
@@ -331,6 +331,7 @@ in each {+cluster+} tier.
      - CPUs (#)
      - Default RAM
      - Default IOPS
+
      - Expected Total Data Size
      - Expected Peak IOPS
      - Suitable For

source/high-availability.txt

@@ -145,7 +145,7 @@ To learn more about how to plan for and respond to disasters, see
 :ref:`arch-center-dr`.
 
 Choose a Deployment Type and Cluster Tier that Fits your Deployment Goals
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+`````````````````````````````````````````````````````````````````````````
 
 When creating a new cluster, you can choose between between a range of {+cluster+} tiers 
 available under the Dedicated, Flex, or Free deployment types. 
@@ -154,7 +154,7 @@ To determine the recommended cluster tier for your
 application size, see the :ref:`arch-center-cluster-size-guide` .
 
 Use an Odd Number of Replica Set Members and Test Failover
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+``````````````````````````````````````````````````````````
 
 To elect a :manual:`primary </core/replica-set-members>`, you need a majority of :manual:`voting </core/replica-set-elections>` replica set members available. We recommend that you create replica sets with an
 odd number of voting replica set members. There is no benefit in having
@@ -187,7 +187,7 @@ You can distribute data across multiple data centers by deploying your {+cluster
 Each availability zone typically contains one or more discrete data centers, each with redundant power, networking and connectivity, often housed in separate
 facilities. When you deploy a dedicated {+cluster+} to a region that supports availability zones, {+service+} automatically splits your {+cluster+}'s 
 nodes across the availability zones. For example, for a three-node replica set {+cluster+} deployed to a region with three availability zones, 
-{+service+} deploys one node in each zone. This ensures that members of the same replica set aren't sharing resources, so that your database remains 
+{+service+} deploys one node in each zone. This ensures that members of the same replica set are not sharing resources, so that your database remains 
 available even if one zone experiences an outage.
 
 To understand the risks associated with using fewer than three data centers, consider the following diagram,