diff --git a/docs/getstarted/installation/resource-and-deployment-architecture-overview.md b/docs/getstarted/installation/resource-and-deployment-architecture-overview.md
index af28be11..099ca50a 100644
--- a/docs/getstarted/installation/resource-and-deployment-architecture-overview.md
+++ b/docs/getstarted/installation/resource-and-deployment-architecture-overview.md
@@ -6,35 +6,32 @@ Learn about the Device42 core resources and how they fit into our deployment arc
 
 ## Device42 Resources
 
-**Main Appliance:** The Device42 Main Appliance is the kick off point for all the discovery
-and insights that will proliferate through your environment. It is a pre-configured virtual
-appliance (built on Linux) that is hosted by the end customer, enabling full protection under the
-client’s data center security architecture and policies.
+### Main Appliance
 
-Device42 operates with only 5 ports open to the virtual appliance:
-- Port 80: redirects to 443
-- Port 443: web (HTTPS)
-- Port 4242: redirects to 4343
-- Port 4343: appliance manager (HTTPS)
-- Port 404: SSH for limited console menu operations
+The Device42 Main Appliance (MA) is the kick-off point for all the discovery and insights that will proliferate through your environment. It is a preconfigured virtual appliance (built on Linux) hosted by the end customer, enabling full protection under the client’s data center security architecture and policies.
 
-**Remote Collector:** The Remote Collector (RC), is a much lighter pre-configured virtual
-appliance (built on Linux), used to perform agentless discovery across network segments. It
-also provides scalability by offloading discovery workloads from the MA. We require that you
-install at least 1 RC with any deployment of Device42.
+Device42 operates with only five ports open to the virtual appliance:
 
-**Windows Discovery Service:** The Windows Discovery Service (WDS) is a .net service which
-runs on a Windows system and makes WMI queries on behalf of the Linux-based RC and MA. If
-you’ll be running Windows discoveries, you will need to deploy at least 1 WDS instance and
-connect it to an RC.
+- **Port 80:** Redirects to port 443
+- **Port 443:** Web (HTTPS)
+- **Port 4242:** Redirects to port 4343
+- **Port 4343:** Appliance manager (HTTPS)
+- **Port 404:** SSH for limited console menu operations
 
-## Deployment Architecture 
+### Remote Collector
 
-Device42 deployment architecture is similar to a hub and spoke model, with each RC/WDS
-collecting data and syncing back to the centralized MA. It is typically recommended for RCs
-and WDS instances to be deployed in pairs, if Windows discovery is required.
+The Remote Collector (RC) is a much lighter preconfigured virtual appliance (built on Linux) used to perform agentless discovery across network segments. It also provides scalability by offloading discovery workloads from the MA. We require you to install at least one RC with any deployment of Device42.
 
-Device42 Deployment Example: Segmented Network
+### Windows Discovery Service
 
-![](/assets/images/deployment-architecture.png)
+The Windows Discovery Service (WDS) is a `.net` service that runs on a Windows system and makes WMI queries on behalf of the Linux-based RC and MA. If you’ll be running Windows discoveries, you will need to deploy at least one WDS instance and connect it to an RC.
+
+## Deployment Architecture
+
+Device42 deployment architecture is similar to a hub-and-spoke model, with each RC/WDS collecting data and syncing back to the centralized MA. It is typically recommended that RCs and WDS instances are deployed in pairs if Windows discovery is required.
 
+### Device42 Deployment Example
+
+The following image illustrates the segmented network structure used for Device42 deployments.
+
+![](/assets/images/deployment-architecture.png)