Removes diagram notes, updates changelog (#71)

Author: sarahsimpers

source/changelog.txt

@@ -15,15 +15,15 @@ What's New in the {+atlas-arch-center+}
 This page lists the changes introduced in each new version of the 
 {+atlas-arch-center+}.
 
-v1
---
+v20250228
+---------
 
-**Released 10 Jan, 2025**
+**Released 28 Feb, 2025**
 
 - Releases the first version of the {+atlas-arch-center+}, including
   guidance to:
 
   - :ref:`Design a landing zone <arch-center-landing-zone>`.
-  - :ref:`Migrate to {+service+} <arch-center-migration>`.
-  - Set up {+service+} in alignment with the {+waf+} by using the
+  - Set up a single-region, single-cloud {+service+} architecture in
+    alignment with the {+waf+}, including example commands for the
     {+atlas-cli+} and Terraform. To get started, see :ref:`arch-center-hierarchy`.

source/disaster-recovery.txt

@@ -83,8 +83,6 @@ data centers.
 Consider the following diagram, which shows data distributed across
 two data centers:
 
-**DIAGRAM BELOW TO BE CHANGED FOR FINAL STYLIZED DIAGRAM**
-
 .. figure:: /includes/images/two-data-centers.png
    :figwidth: 750px
    :alt: An image showing two data centers: Data Center 1, with a primary and a secondary node, and Data Center 2, with only a secondary node
@@ -95,8 +93,6 @@ out of three replica set members available, no majority, and the system degrades
 Consider the following diagram, which shows data distributed across
 three data centers:
 
-**DIAGRAM BELOW TO BE CHANGED FOR FINAL STYLIZED DIAGRAM**
-
 .. figure:: /includes/images/three-data-centers.png
    :figwidth: 750px
    :alt: An image showing three data centers: Data Center 1, with a primary node, Data Center 2, with a secondary node, and Data Center 3, with a secondary node
@@ -139,8 +135,6 @@ Consider the following diagram, which shows a sharded {+cluster+}
 spread across three data centers. The application connects to the {+cluster+} from a remote location. If Data Center 3 becomes unavailable, the application can still connect to the ``mongos``
 processes in the other data centers.
 
-**DIAGRAM BELOW TO BE CHANGED FOR FINAL STYLIZED DIAGRAM**
-
 .. figure:: /includes/images/mongos-three-data-centers.png
    :figwidth: 750px
    :alt: An image showing three data centers: Data Center 1, with a primary shards and two mongos, Data Center 2, with secondary shards and two mongos, and Data Center 3, with secondary shards and two mongos. The application connects to all six mongos instances.

source/high-availability.txt

@@ -33,8 +33,6 @@ entire selection and failover process happens within seconds, without manual
 intervention. MongoDB optimizes the algorithms used to detect failure and elect a 
 new primary, reducing the failover interval. 
 
-[insert diagram]
-
 Clusters that you deploy within a single region are spread across availability 
 zones within that region, so that they can withstand partial region outages without 
 an interruption of read or write availability. You can optionally choose to spread 

source/landing-zone.txt

@@ -211,8 +211,6 @@ The following example diagram unifies many of the architectural diagrams
 across the {+atlas-arch-center+} in one image to visualize your
 landing zone. You can adjust it as needed to customize it for your organization.
 
-**DIAGRAM BELOW TO BE CHANGED FOR FINAL DIAGRAM**
-
 .. figure:: /includes/images/LandingZone.svg
    :alt: "A diagram showing an example {+service+} landing zone."
    :align: center