diff --git a/website/content/vagrant-cloud/boxes/architecture.mdx b/website/content/vagrant-cloud/boxes/architecture.mdx
index d7a0dfa22..ea6b8c309 100644
--- a/website/content/vagrant-cloud/boxes/architecture.mdx
+++ b/website/content/vagrant-cloud/boxes/architecture.mdx
@@ -11,8 +11,8 @@ multiple architecture options. This allows you to have multiple instances
 of one specific provider. The specific provider shares a common name for
 artifacts of different architectures.
 
-Using the `hashicorp/precise32` and `hashicorp/precise64` boxes as an example,
-each of these boxes include a provider for `virtualbox`. This looks like:
+For example, the `hashicorp/precise32` and `hashicorp/precise64` boxes each
+include a provider for `virtualbox`.
 
 ```
 hashicorp/precise32
@@ -27,7 +27,7 @@ hashicorp/precise64
 The addition of architecture now allows these to be combined into a single
 box. Instead of having a `hashicorp/precise32` box for a 32-bit guest, and 
 a `hashicorp/precise64` box for a 64-bit guest, a single `hashicorp/precise`
-box can provider both. The new box would look like:
+box can provide both.
 
 ```
 hashicorp/precise
@@ -36,9 +36,9 @@ hashicorp/precise
     provider: virtualbox, architecture: i386
 ```
 
-The Vagrant CLI will automatically match the
-provider architecture using the detected local host architecture. If the
-Vagrant CLI cannot find a matching architecture, it will attempt a
+The Vagrant CLI will automatically match the provider architecture using the
+detected local host architecture. If the Vagrant CLI cannot find a matching 
+architecture, it will attempt a
 [special case match](/vagrant/vagrant-cloud/boxes/architecture#unknown-architecture).
 
 ## Default architecture
@@ -53,9 +53,8 @@ Note, this functionality enables backwards compatiblity
 with previous versions of the Vagrant CLI that do not support architecture
 filtering when matching an appropriate provider.
 
-For example, after creating 
-the `2.0.0` version of the `hashicorp/precise` box and creating a new 
-provider for `virtualbox` with `amd64` architecture it would look like:
+For example, the `2.0.0` version of the `hashicorp/precise` box is created and 
+a new `virtualbox` provider is created with `amd64` architecture.
 
 ```
 hashicorp/precise
@@ -63,8 +62,7 @@ hashicorp/precise
     provider: virtualbox, architecture: amd64, default_architecture: true
 ```
 
-If another `virtualbox` provider is created with `i386` architecture it would
-then look like:
+Adding another `virtualbox` provider with `i386` architecture.
 
 ```
 hashicorp/precise
@@ -77,7 +75,8 @@ When the Vagrant CLI, prior to version 2.4.0, requests the `hashicorp/precise`
 box with the `virtualbox` provider, it will receive the information from 
 the `virtualbox` provider with the `amd64` architecture because it is flagged 
 as being the default architecture. If, instead, the provider with `i386`
-architecture should be returned, the provider can be updated to look like:
+architecture should be returned, the `virtualbox` provider for the `i386` 
+architecture can be updated to be the default architecture.
 
 ```
 hashicorp/precise