Apply suggestions from code review

Author: viniciusdc

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

@@ -128,23 +128,30 @@ amazon_web_services:
         # Replace with your custom AMI ID
         ami_id: ami-0abcdef1234567890
         # Command to run before the node joins the cluster
-        pre_bootstrap_command: "echo 'Hello, World!'"
-```
+        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"
 
 **Parameters:**
 
-- `ami_id` (Optional): The ID of the custom AMI to use for the nodes in this group. If specified, the `ami_type` is automatically set to `CUSTOM`.
+- `ami_id` (Optional): The ID of the custom AMI to use for the nodes in this group; this assumes the AMI provided is an EKS-optimized AMI derivative. If specified, the `ami_type` is automatically set to `CUSTOM`.
 - `pre_bootstrap_command` (Optional): A command or script to execute on the node before
   it joins the Kubernetes cluster. This can be used for custom setup or configuration
   tasks. The format should be a single string in conformation with the shell syntax.
   This command is injected in the `user_data` field of the launch template. For more
   information, see [User Data](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html).
 
+> If you're using a `launch_template` with a custom `ami_id`, there's an issue with updating the `scaling`.desired_size` via Nebari configuration (terraform). To scale up, you must recreate the node group or adjust the scaling settings directly in the AWS Console UI (recommended). We are aware of this inconsistency and plan to address it in a future update.
+
 :::note
 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 you
-cluster region by inspecting its respective SSM parameter. For more information, see
-[Retrieve recommended Amazon Linux AMI IDs](https://docs.aws.amazon.com/eks/latest/userguide/retrieve-ami-id.html).
+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). 
 :::
 
 </TabItem>