diff --git a/build/pooling.md b/build/pooling.md
index cd15b2d21..1ceea8304 100644
--- a/build/pooling.md
+++ b/build/pooling.md
@@ -2,19 +2,7 @@
 
 ## Introduction
 
-The DSS is designed to be deployed in a federated manner where multiple
-organizations each host a DSS instance, and all of those instances interoperate.
-Specifically, if a change is made on one DSS instance, that change may be read
-from a different DSS instance.  A set of interoperable DSS instances is called a
-"pool", and the purpose of this document is to describe how to form and maintain
-a DSS pool.
-
-It is expected that there will be exactly one production DSS pool for any given
-DSS region, and that a DSS region will generally match aviation jurisdictional
-boundaries (usually national boundaries).  A given DSS region (e.g.,
-Switzerland) will likely have one pool for production operations, and an
-additional pool for partner qualification and testing (per, e.g.,
-F3411-19 A2.6.2).
+The content of this section has been migrated to [Introduction](../deploy/architecture.md#introduction).
 
 ### Terminology notes
 
diff --git a/deploy/README.md b/deploy/README.md
index 98101f781..6214fa3eb 100644
--- a/deploy/README.md
+++ b/deploy/README.md
@@ -4,7 +4,7 @@
 
 ## Introduction
 
-An operational DSS deployment requires a specific architecture to be compliant with [standards requirements](../README.md#standards-and-regulations) and meet performance expectations as described in [architecture](./architecture.md).
+An operational DSS deployment requires a specific architecture to be compliant with [standards requirements](../README.md#standards-and-regulations) and meet performance expectations as described in [Deployment of a DSS Pool](./architecture.md).
 
 ## Deployment options
 
diff --git a/deploy/architecture.md b/deploy/architecture.md
index 23aedc9e9..43f219220 100644
--- a/deploy/architecture.md
+++ b/deploy/architecture.md
@@ -1,8 +1,20 @@
-# Kubernetes deployment
+# Deployment of a DSS Pool
 
 ## Introduction
 
-See [introduction](../build/pooling.md#introduction)
+The DSS is designed to be deployed in a federated manner where multiple
+organizations each host a DSS instance, and all of those instances interoperate.
+Specifically, if a change is made on one DSS instance, that change may be read
+from a different DSS instance.  A set of interoperable DSS instances is called a
+"pool", and the purpose of this document is to describe how to form and maintain
+a DSS pool.
+
+It is expected that there will be exactly one production DSS pool for any given
+DSS region, and that a DSS region will generally match aviation jurisdictional
+boundaries (usually national boundaries).  A given DSS region (e.g.,
+Switzerland) will likely have one pool for production operations, and an
+additional pool for partner qualification and testing (per, e.g.,
+F3411-19 A2.6.2).
 
 ## Architecture