apply commit fixes

Author: viniciusdc

docs/docs/explanations/advanced-provider-configuration.md

@@ -114,7 +114,7 @@ To avoid unexpected downtime or data loss, consider creating a new node group wi
 
 To configure a launch template for a node group in your `nebari-config.yaml`, add the `launch_template` section under the desired node group:
 
-```yaml
+````yaml
 amazon_web_services:
   region: us-west-2
   kubernetes_version: "1.18"
@@ -129,12 +129,12 @@ amazon_web_services:
         ami_id: ami-0abcdef1234567890
         # Command to run before the node joins the cluster
         pre_bootstrap_command: |
-       		#!/bin/bash
-       		# This script is executed before the node is bootstrapped
-       		# You can use this script to install additional packages or configure the node
-       		# For example, to install the `htop` package, you can run:
-       		# sudo apt-get update
-       		# sudo apt-get install -y htop"
+       	  #!/bin/bash
+       	  # This script is executed before the node is bootstrapped
+       	  # You can use this script to install additional packages or configure the node
+       	  # For example, to install the `htop` package, you can run:
+       	  # sudo apt-get update
+       	  # sudo apt-get install -y htop"
 
 **Parameters:**
 
@@ -151,7 +151,7 @@ amazon_web_services:
 If an `ami_id` is not provided, AWS will use the default Amazon Linux 2 AMI for the
 specified instance type. You can find the latest optimized AMI IDs for Amazon EKS in your
 cluster region by inspecting its respective SSM parameters. For more information, see
-[Retrieve recommended Amazon Linux AMI IDs](https://docs.aws.amazon.com/eks/latest/userguide/retrieve-ami-id.html). 
+[Retrieve recommended Amazon Linux AMI IDs](https://docs.aws.amazon.com/eks/latest/userguide/retrieve-ami-id.html).
 :::
 
 </TabItem>
@@ -181,7 +181,7 @@ azure:
       min_nodes: 0
       max_nodes: 5
   storage_account_postfix: t65ft6q5
-```
+````
 
 </TabItem>