return legacy section docs

mozilla-services · Jun 7, 2024 · 4bda5c7 · 4bda5c7
1 parent a4b4652
commit 4bda5c7
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/docs/src/architecture.md b/docs/src/architecture.md
@@ -128,8 +128,9 @@ router record for a `UAID`.
 | router_type  | Router Type (See [`autoendpoint::extractors::routers::RouterType`])              |
 | node_id      | Hostname of the connection node the client is connected to.                      |
 | connected_at | Precise time (in milliseconds) the client connected to the node.                 |
-| curmonth     | Message table name to use for storing `WebPush` messages.                        |
 | last_connect | **global secondary index** - year-month-hour that the client has last connected. |
+| curmonth     | Message table name to use for storing `WebPush` messages.                        |
+
 
 Autopush DynamoDB used an optimistic deletion policy for `node_id` to avoid
 delete calls when not needed. During a delivery attempt, the endpoint

diff --git a/docs/src/table_rotation.md b/docs/src/table_rotation.md
@@ -36,7 +36,7 @@ on the prior month may then be lowered.
 ## DynamoDB Rotating Message Table Interaction Rules (legacy)
 
 Due to the complexity of having notifications spread across two tables,
-several rules are used to avoid losing messages during the month
+several rules were used to avoid losing messages during the month
 transition.
 
 The logic for connection nodes is more complex, since only the