fix(ins): fix create doc for windows and typos (#3854)

bene2k1 · ldecarvalho-doc · web-flow · commit 46b03df5e196 · 2024-10-21T10:51:36.000+02:00
* fix(ins): fix create doc for windows and typos

* Update compute/instances/how-to/create-an-instance.mdx

* docs(ins): fix typo

* Apply suggestions from code review

Co-authored-by: ldecarvalho-doc &lt;82805470+ldecarvalho-doc@users.noreply.github.com&gt;

---------

Co-authored-by: ldecarvalho-doc &lt;82805470+ldecarvalho-doc@users.noreply.github.com&gt;
diff --git a/compute/instances/how-to/create-an-instance.mdx b/compute/instances/how-to/create-an-instance.mdx
@@ -34,10 +34,10 @@ Select a tab below for instructions on how to create an Instance via either our
         - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed.
         - **Choose an Instance type**. <br />
           Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/compute/instances/reference-content/choosing-instance-type/).
-        - ***Choose an Image** to run on your Instance. <br />
+        - **Choose an image** to run on your Instance. <br />
           This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/compute/instances/reference-content/images-and-instantapps/).
-        - **Name** your Instance, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance.
-        - **Add Volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up up to 16 local and/or block type volumes as needed.
+        - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance.
+        - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed.
           <Message type="important">
              - Ensure that the volume containing your OS image has a minimum size of 10 GB. For a GPU OS, the recommended size is 125 GB.
              - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/compute/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume).
@@ -50,7 +50,7 @@ Select a tab below for instructions on how to create an Instance via either our
               You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance.
             </Message>
         - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
-          You can configure a cloud-init script to automate instance setup, such as setting up software, users, and system configurations at the first boot.
+          You can configure a cloud-init script to automate Instance setup, such as setting up software, users, and system configurations at the first boot.
         - **Verify the [SSH keys](/console/account/concepts/#ssh-key)** that will give you access to your Instance.
         - **Verify the Estimated cost** of your Instance, based on the specifications you chose.
     4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready.
@@ -71,23 +71,24 @@ Select a tab below for instructions on how to create an Instance via either our
     2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays.
     3. Complete the following steps:
         - Choose an **Availability Zone**, which represents the geographical region where your Instance will be deployed.
-        - Choose a **POP2-WIN** Instance type from the **Production-Optimized** range.
-        - Choose a **Windows Server** Image to run on your Instance.
-          - Add **Volumes**, which are storage spaces used by your Instances. You can add several block volumes and define how much storage you want for each.
+        - **Choose a POP2-WIN** Instance type from the **Production-Optimized** range.
+        - **Choose a Windows Server image** to run on your Instance.
+        - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance.
+        - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed.
           <Message type="important">
-             - Ensure that a volume with a Windows image has a minimum capacity of 25 GB.
+             - Ensure that a volume containing a Windows Server image has a minimum capacity of 25 GB.
              - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/compute/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume).
              - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes.
           </Message>
-        - Configure the network of the Instance. You can either select to use **Routed public IP** (a dedicated public IP address routed to your Instance that allows direct communication between the Instance and the Internet) or a **NAT public IP** (a public IP address that uses a carrier-grade NAT to translate the Instances NAT IP address). If you are unsure which to use, we recommend a routed public IP for ease of use and improved performance.
+        - **Configure network** of the Instance.
           - Leave the checkbox ticked to assign a **Public IPv4** to the Instance. You can either allocate a new IPv4 address or select one or multiple existing IPv4s. Alternatively, uncheck the box if you do not want an IPv4.
           - Leave the checkbox ticked to assign a **Public IPv6** to the Instance. You can either allocate a new IPv6 address or select one or multiple existing IPv6s. Alternatively, uncheck the box if you do not want an IPv6.
             <Message type="tip">
-              You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses.
+              You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance.
             </Message>
-        - Enter a **Name** for your Instance, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance.
-        - Click **Advanced options** if you want to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
-        - Choose the [RSA SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair) that will give you access to your Instance. If you do not have an RSA SSH key yet, click **Add RSA SSH key** and follow the steps indicated.
+        - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
+          You can configure a cloud-init script to automate Instance setup, such as setting up software, users, and system configurations at the first boot.
+        - **Choose the [RSA SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair)** that will give you access to your Instance. If you do not have an RSA SSH key yet, click **Add RSA SSH key** and follow the steps indicated.
         - Verify the **Estimated cost** of your Instance, based on the specifications you chose.
     4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready.
 
diff --git a/compute/instances/quickstart.mdx b/compute/instances/quickstart.mdx
@@ -29,10 +29,10 @@ Scaleway [Instances](/compute/instances/concepts/#instance) are computing units
         - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed.
         - **Choose an Instance type**. <br />
           Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/compute/instances/reference-content/choosing-instance-type/).
-        - ***Choose an Image** to run on your Instance. <br />
+        - ***Choose an image** to run on your Instance. <br />
           This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/compute/instances/reference-content/images-and-instantapps/).
-        - **Name** your Instance, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance.
-        - **Add Volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up up to 16 local and/or block type volumes as needed.
+        - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance.
+        - **Add Volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed.
           <Message type="important">
              - Ensure that the volume containing your OS image has a minimum size of 10 GB. For a GPU OS, the recommended size is 125 GB.
              - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/compute/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume).
@@ -45,7 +45,7 @@ Scaleway [Instances](/compute/instances/concepts/#instance) are computing units
               You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance.
             </Message>
         - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
-          You can configure a cloud-init script to automate instance setup, such as setting up software, users, and system configurations at the first boot.
+          You can configure a cloud-init script to automate Instance setup, such as setting up software, users, and system configurations at the first boot.
         - **Verify the [SSH keys](/console/account/concepts/#ssh-key)** that will give you access to your Instance.
         - **Verify the Estimated cost** of your Instance, based on the specifications you chose.
     4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready.
