update for backbone

ace_backbone/docs/backbone.md

@@ -337,12 +337,13 @@ Now that you have established the peering between the two CSPs, you have achieve
 
 Let's carry on with the final deployment of the connectivity to the on-prem DC.
 
-Before configuring the attachments between the Secure Edge Gateway and the Transit Gateways, you have to esnure thta the Transit Gateways cluster earlier deployed in AWS is configured with a **`BGP AS number`**. <ins>This is a prerequisite for completing the Edge's deployment</ins>!
+Before configuring the attachments between the Secure Edge Gateway and the Transit Gateways, you have to ensure thta the Transit Gateways cluster earlier deployed in AWS is configured with a **`BGP AS number`**. <ins>This is a prerequisite for completing the Edge's deployment</ins>!
 
 Go to **CoPilot > Cloud Fabric > Gateways > Transit Gateways** and click on the **transit-aws** cluster!
 
 ```{figure} images/backbone-tgw019.png
 ---
+height: 400px
 align: center
 ---
 transit-aws
@@ -361,6 +362,7 @@ After this task, this is how the overall topology would look like.
 
 ```{figure} images/backbone-tgw021.png
 ---
+height: 400px
 align: center
 ---
 Topology after task #6

docs/ace-backbone/_sources/docs/backbone.md

@@ -337,12 +337,13 @@ Now that you have established the peering between the two CSPs, you have achieve
 
 Let's carry on with the final deployment of the connectivity to the on-prem DC.
 
-Before configuring the attachments between the Secure Edge Gateway and the Transit Gateways, you have to esnure thta the Transit Gateways cluster earlier deployed in AWS is configured with a **`BGP AS number`**. <ins>This is a prerequisite for completing the Edge's deployment</ins>!
+Before configuring the attachments between the Secure Edge Gateway and the Transit Gateways, you have to ensure thta the Transit Gateways cluster earlier deployed in AWS is configured with a **`BGP AS number`**. <ins>This is a prerequisite for completing the Edge's deployment</ins>!
 
 Go to **CoPilot > Cloud Fabric > Gateways > Transit Gateways** and click on the **transit-aws** cluster!
 
 ```{figure} images/backbone-tgw019.png
 ---
+height: 400px
 align: center
 ---
 transit-aws
@@ -361,6 +362,7 @@ After this task, this is how the overall topology would look like.
 
 ```{figure} images/backbone-tgw021.png
 ---
+height: 400px
 align: center
 ---
 Topology after task #6

docs/ace-backbone/docs/backbone.html

@@ -642,10 +642,10 @@ <h2>Task #5: Attach Transit Gateways to aws-tgw<a class="headerlink" href="#task
 <h2>Task #6: Configure BGP ASN<a class="headerlink" href="#task-6-configure-bgp-asn" title="Link to this heading">#</a></h2>
 <p>Now that you have established the peering between the two CSPs, you have achieved the <strong><code class="docutils literal notranslate"><span class="pre">Aviatrix</span> <span class="pre">Cloud</span> <span class="pre">Backbone</span></code></strong>.</p>
 <p>Let’s carry on with the final deployment of the connectivity to the on-prem DC.</p>
-<p>Before configuring the attachments between the Secure Edge Gateway and the Transit Gateways, you have to esnure thta the Transit Gateways cluster earlier deployed in AWS is configured with a <strong><code class="docutils literal notranslate"><span class="pre">BGP</span> <span class="pre">AS</span> <span class="pre">number</span></code></strong>. <ins>This is a prerequisite for completing the Edge’s deployment</ins>!</p>
+<p>Before configuring the attachments between the Secure Edge Gateway and the Transit Gateways, you have to ensure thta the Transit Gateways cluster earlier deployed in AWS is configured with a <strong><code class="docutils literal notranslate"><span class="pre">BGP</span> <span class="pre">AS</span> <span class="pre">number</span></code></strong>. <ins>This is a prerequisite for completing the Edge’s deployment</ins>!</p>
 <p>Go to <strong>CoPilot &gt; Cloud Fabric &gt; Gateways &gt; Transit Gateways</strong> and click on the <strong>transit-aws</strong> cluster!</p>
 <figure class="align-center" id="id21">
-<img alt="../_images/backbone-tgw019.png" src="../_images/backbone-tgw019.png" />
+<a class="reference internal image-reference" href="../_images/backbone-tgw019.png"><img alt="../_images/backbone-tgw019.png" src="../_images/backbone-tgw019.png" style="height: 400px;" /></a>
 <figcaption>
 <p><span class="caption-number">Fig. 21 </span><span class="caption-text">transit-aws</span><a class="headerlink" href="#id21" title="Link to this image">#</a></p>
 </figcaption>
@@ -659,7 +659,7 @@ <h2>Task #6: Configure BGP ASN<a class="headerlink" href="#task-6-configure-bgp-
 </figure>
 <p>After this task, this is how the overall topology would look like.</p>
 <figure class="align-center" id="id23">
-<img alt="../_images/backbone-tgw021.png" src="../_images/backbone-tgw021.png" />
+<a class="reference internal image-reference" href="../_images/backbone-tgw021.png"><img alt="../_images/backbone-tgw021.png" src="../_images/backbone-tgw021.png" style="height: 400px;" /></a>
 <figcaption>
 <p><span class="caption-number">Fig. 23 </span><span class="caption-text">Topology after task #6</span><a class="headerlink" href="#id23" title="Link to this image">#</a></p>
 </figcaption>

docs/immersion-day/_sources/docs/lab0.md

@@ -1,3 +1,4 @@
 # Lab 0: Deploy Aviatrix using Automation
 
+
 [Click here to open the lab guide for Lab 0](pdfs/immersion-day-lab0.pdf)