diff --git a/public/docs/css/main.css b/public/docs/css/main.css
index 8c59b348a0..06c5ed2045 100644
--- a/public/docs/css/main.css
+++ b/public/docs/css/main.css
@@ -439,6 +439,14 @@ table th {
   padding: 0.8rem 1rem;
 }
 
+.table-full-width table {
+  width: 100%;
+}
+
+.table-full-width th {
+  text-align: left;
+}
+
 .credits table,
 .credits thead,
 .credits tbody,
diff --git a/src/pages/docs/infrastructure/index.mdx b/src/pages/docs/infrastructure/index.mdx
index 7f7e03ec4d..1552de01de 100644
--- a/src/pages/docs/infrastructure/index.mdx
+++ b/src/pages/docs/infrastructure/index.mdx
@@ -21,16 +21,20 @@ You assign deployment targets to an environment and you can set up a lifecycle t
 
 Target tags also make applying the same process to all environments easier. The table below shows a matrix of target tags and environments, with environments having different resource sets. Deployments proceed in an orderly fashion across the matrix.
 
-| | <div style="width:175px">Development</div> | <div style="width:175px">Staging</div> | Production |
-| ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------ | ------------------------------------------------------------------------ | -------------- |
-| Web tag                | Dev-Target-1     | Staging-Target-1<br />Staging-Target-2     | Production-Target-1<br />Production-Target-2<br />Production-Target-3 |
-| API tag | Dev-Target-2     | Staging-Target-3<br />Staging-Target-4     | Production-Target-4<br />Production-Target-5 |
-| Database tag | Dev-Target-3 | Staging-Target-5 | Production-Target-6<br />Production-Target-7 |
+:::div{.table-full-width}
+
+|              | <div style="width:175px">Development</div> | <div style="width:175px">Staging</div> | Production                                                            |
+| ------------ | ------------------------------------------ | -------------------------------------- | --------------------------------------------------------------------- |
+| Web tag      | Dev-Target-1                               | Staging-Target-1<br />Staging-Target-2 | Production-Target-1<br />Production-Target-2<br />Production-Target-3 |
+| API tag      | Dev-Target-2                               | Staging-Target-3<br />Staging-Target-4 | Production-Target-4<br />Production-Target-5                          |
+| Database tag | Dev-Target-3                               | Staging-Target-5                       | Production-Target-6<br />Production-Target-7                          |
+
+:::
 
 You can manage the machines and services you deploy your software to on the **Infrastructure** tab of the Octopus Web Portal:
 
 :::figure
-![](/docs/img/infrastructure/images/infrastructure-overview-dashboard.png)
+![The Infrastructure overview dashboard in the Octopus Web Portal](/docs/img/infrastructure/images/infrastructure-overview-dashboard.png)
 :::
 
 There are a few key infrastructure concepts in Octopus Deploy:
@@ -48,4 +52,4 @@ There are a few key infrastructure concepts in Octopus Deploy:
 - [Deployment targets](/docs/infrastructure/deployment-targets)
 - [Workers](/docs/infrastructure/workers)
 - [Accounts](/docs/infrastructure/accounts)
-- [Signing keys](/docs/infrastructure/signing-keys)
\ No newline at end of file
+- [Signing keys](/docs/infrastructure/signing-keys)