fix(gen): update codeblocks from sh to bash

macros/serverless-jobs/automate-resources-management.mdx

@@ -49,19 +49,19 @@ Serverless Jobs are perfectly adapted for these autonomous tasks, as we do not n
 
 9. In the **Execution** tab, define the desired Scaleway CLI command, as shown in the examples below:
     - **Power Instances on and off**
-        ```sh
+        ```bash
         # Power on
         /scw instance server start 11111111-1111-1111-1111-111111111111
 
         # Power off
         /scw instance server stop 11111111-1111-1111-1111-111111111111
         ```
     - **Create a snapshot of an Instance volume**
-        ```sh
+        ```bash
         /scw instance snapshot create volume-id=11111111-1111-1111-1111-111111111111
         ```
     - **Create a backup of an Instance**
-        ```sh
+        ```bash
         /scw instance server backup 11111111-1111-1111-1111-111111111111
         ```
 10. Click **Create job**.

pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx

@@ -39,7 +39,7 @@ You can connect directly to the terminal of your Mac mini using the SSH protocol
 
 4. Open your terminal application and use the SSH command provided on the **Overview** page to connect.
    - The SSH command will be in the format:
-     ```sh
+     ```bash
      ssh your_mac_mini_username@<your_mac_mini_ip>
      ```
    - Replace `<your_mac_mini_username>` with your Mac mini username.

pages/apple-silicon/how-to/update-os-mac-mini.mdx

@@ -59,16 +59,16 @@ The recommended method to update the macOS is to reinstall your Mac mini with an
 To manually update the operating system using the `softwareupdate` tool, follow these steps:
 
 1. List all available updates:
-    ```sh
+    ```bash
     softwareupdate --list
     ```
 2. Install all available updates:
-    ```sh
+    ```bash
     sudo softwareupdate --install
     ```
     <Message type="tip">
         If you want to upgrade selected packages only, use the following command:
-        ```sh
+        ```bash
         softwareupdate --install package-name
         ```
     </Message>

pages/apple-silicon/quickstart.mdx

@@ -70,7 +70,7 @@ Refer to our detailed documentation for Windows, Linux, and macOS for OS specifi
 3. Click the name of the Mac mini you want to connect to. The **Overview** page for your selected Mac mini displays.
 4. Open your terminal application and use the SSH command provided on the **Overview** page to connect.
    - The SSH command will be in the format:
-     ```sh
+     ```bash
      ssh your_mac_mini_username@<your_mac_mini_ip>
      ```
    - Replace `<your_mac_mini_username>` with your Mac mini username.

pages/apple-silicon/troubleshooting/cant-connect-using-ssh.mdx

@@ -50,7 +50,7 @@ Repeated failed login attempts can trigger Scaleway’s security mechanisms, blo
 
 #### Attempt SSH connection again
 After the reboot, attempt to reconnect using:
-```sh
+```bash
 ssh -i /path/to/your/private_key user@<server_ip>
 ```
 Replace `/path/to/your/private_key` with your actual private key location and `<server_ip>` with your Mac mini’s IP address.

pages/apple-silicon/troubleshooting/cant-connect-using-vnc.mdx

@@ -36,7 +36,7 @@ You are unable to establish a remote desktop (VNC) connection to your Scaleway M
 
 #### Verify the server status
 Run the following command in a terminal:
-```sh
+```bash
 ping -c 5 <server_ip>
 ```
 If `ping` fails:
@@ -49,7 +49,7 @@ If `ping` fails:
 
 #### Verify the VNC connection
 Run the following command:
-```sh
+```bash
 nc -zv <server_ip> <vnc_port>
 ```
 If the connection fails:
@@ -59,7 +59,7 @@ If the connection fails:
 
 #### Verify the SSH server response
 Run the command:
-```sh
+```bash
 nc -zv <server_ip> 22
 ```
 If the connection fails, [reboot the server](/apple-silicon/how-to/reboot-mac-mini/).
@@ -84,26 +84,26 @@ If all else fails, [reinstall macOS](/apple-silicon/how-to/reinstall-mac-mini/)
 
 ### Enabling and configuring Packet Filter (pf)
 1. Open the pf configuration file in a text editor to restrict access to screen sharing:
-    ```sh
+    ```bash
     sudo nano /etc/pf.conf
     ```
 2. Add the following lines to the file and save it:
-    ```sh
+    ```bash
     block in on en0 proto tcp from any to any port 5900
     pass in on en0 proto tcp from <static IP> to any port 5900
     ```
 3. Apply the configuration:
-    ```sh
+    ```bash
     sudo pfctl -f /etc/pf.conf
     ```
 
 ### Restarting screen sharing via SSH
 1. Connect via SSH:
-    ```sh
+    ```bash
     ssh your_mac_mini_username@<your_mac_mini_ip>
     ```
 2. Restart screen sharing:
-    ```sh
+    ```bash
     sudo killall screensharingd
     ```
 

pages/container-registry/troubleshooting/common-errors-when-pushing-images-to-container-registry.mdx

@@ -30,18 +30,18 @@ You are unable to push images to Scaleway's Container Registry.
 
 ### Review error messages and logs
 - Run the push command with verbose output for more details:
-  ```sh
+  ```bash
   docker push --debug <your-image>
   ```
 - Check the Docker client logs for warnings or errors:
-  ```sh
+  ```bash
   docker logs <container_id>
   ```
 - Verify Scaleway’s Container Registry [status](https://status.scaleway.com/) for any ongoing incidents.
 
 ### Check Docker configuration and version
 - Ensure your Docker client is up-to-date by running:
-  ```sh
+  ```bash
   docker --version
   ```
 - Check for configuration errors in the Docker daemon and client.
@@ -58,7 +58,7 @@ You are unable to push images to Scaleway's Container Registry.
 
 ## Additional troubleshooting steps
 - Try pushing a small test image to verify general functionality:
-  ```sh
+  ```bash
   docker pull alpine && docker tag alpine <your-registry>/test-image && docker push <your-registry>/test-image
   ```
 - Review Docker’s official [troubleshooting guides](https://docs.docker.com/tags/troubleshooting/) for further insights.

pages/data-warehouse/how-to/connect-applications.mdx

@@ -40,7 +40,7 @@ To connect your deployment with BI tools, refer to the [dedicated documentation]
 
         <Tabs id="data-warehouse-connect-protocols">
             <TabsTab label="ClicHouse® CLI">
-            ```sh
+            ```bash
             clickhouse client \
             --host <YOUR_DEPLOYMENT_ID>.dtwh.<REGION>.scw.cloud \
             --port 9440 \
@@ -50,7 +50,7 @@ To connect your deployment with BI tools, refer to the [dedicated documentation]
             ```
             </TabsTab>
             <TabsTab label="MySQL">
-            ```sh
+            ```bash
               mysql -h <YOUR_DEPLOYMENT_ID>.dtwh.<REGION>.scw.cloud \
               -P 9004 \
               -u scwadmin \
@@ -61,7 +61,7 @@ To connect your deployment with BI tools, refer to the [dedicated documentation]
             </Message>
             </TabsTab>
             <TabsTab label="HTTPS">
-            ```sh
+            ```bash
             echo 'SELECT 1' | curl 'https://scwadmin:<PASSWORD>@<YOUR_DEPLOYMENT_ID>.dtwh.<REGION>.scw.cloud:8443' -d @-
             ```
             <Message type="note">

pages/data-warehouse/how-to/import-data.mdx

@@ -34,7 +34,7 @@ Scaleway Data Warehouse for ClickHouse® allows you to quickly import any type o
 
 5. In a terminal, paste and execute the copied command to connect to your deployment. Make sure to replace the placeholders with the corresponding values.
 
-    ```sh
+    ```bash
     clickhouse client \
     --host <YOUR_DEPLOYMENT_URL> \
     --port 9440 \
@@ -71,7 +71,7 @@ The `s3` Storage Engine creates a table that points to a data table stored in an
 </TabsTab>
 <TabsTab label="ClickHouse® Client">
 The `clickhouse-client` executes an INSERT query to populate a table in your deployment by specifying the URL of the source Object Storage bucket and the file format.
-  ```sh
+  ```bash
   clickhouse-client --query="INSERT INTO your_table FORMAT CSVWithNames" \
   --url "https://my-bucket.s3.scaleway.com/data/my_data.csv" \
   --input_format_with_names=1

pages/data-warehouse/quickstart.mdx

@@ -68,7 +68,7 @@ You can now execute SQL commands.
 
 3. Copy the ClickHouse® CLI command, and execute it in a terminal to connect to your deployment. Make sure to replace the placeholders beforehand.
 
-    ```sh
+    ```bash
     clickhouse client \
     --host <YOUR_DEPLOYMENT_ID>.dtwh.<REGION>.scw.cloud \
     --port 9440 \

pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx

@@ -33,7 +33,7 @@ Find below examples of network interface configurations on different distributio
 Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for configuring network interfaces. For older releases, refer to the Debian configuration.
 
 1. Log into your virtual machine and open the network configuration file `/etc/netplan/01-netcfg.yaml` in a text editor of your choice:
-    ```sh
+    ```bash
     sudo nano /etc/netplan/01-netcfg.yaml
     ```
 2. Create a network configuration as follows. Replace `<failover_IP>` with your failover IP address:
@@ -55,14 +55,14 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for
     ```
 3. Save the file and exit the text editor.
 4. Apply the new configuration:
-    ```sh
+    ```bash
     sudo netplan apply
     ```
 
 ## Debian
 
 1. Log into the virtual machine and edit the network configuration file:
-    ```sh
+    ```bash
     sudo nano /etc/network/interfaces
     ```
 2. Configure the network interface as follows. Replace `<failover_IP>` with your failover IP address:
@@ -76,7 +76,7 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for
     ```
 3. Save the file and exit the text editor.
 4. Set the DNS server information:
-    ```sh
+    ```bash
     sudo nano /etc/resolv.conf
     ```
 5. Add the following DNS resolvers:
@@ -85,18 +85,18 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for
     nameserver 51.159.47.26
     ```
 6. Activate the network on your virtual machine:
-    ```sh
+    ```bash
     sudo ifup eth0
     ```
     *Alternatively, you can restart networking with:*
-    ```sh
+    ```bash
     sudo systemctl restart networking
     ```
 
 ## CentOS
 
 1. Log into the virtual machine and edit the network configuration file:
-    ```sh
+    ```bash
     sudo nano /etc/sysconfig/network-scripts/ifcfg-eth0
     ```
 2. Configure the network interface as follows. Replace `<failover_IP>` with your failover IP address and `<virtual_MAC>` with the virtual MAC of the VM:
@@ -118,7 +118,7 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for
     ```
 3. Save and close the text editor.
 4. Create or edit the routing configuration file:
-    ```sh
+    ```bash
     sudo nano /etc/sysconfig/network-scripts/route-eth0
     ```
     Add the following lines:
@@ -127,7 +127,7 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for
     default via 62.210.0.1 dev eth0
     ```
 5. Activate the network interface:
-    ```sh
+    ```bash
     sudo ifup eth0
     ```
 

pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx

@@ -39,11 +39,11 @@ You can add failover IP addresses to each server based on your offer and service
   Reverse DNS updates may take some time to propagate. You can verify changes using the following commands:
 
   - Linux/macOS:
-    ```sh
+    ```bash
     dig -x <failover_IP>
     ```
   - Windows:
-    ```sh
+    ```bash
     nslookup <failover_IP>
     ```
 </Message>

pages/dedibox/how-to/use-dedibackup-ftp-backup.mdx

@@ -118,7 +118,7 @@ To connect to the Dedibackup service, we recommend `lftp` for interactive use an
 #### Example of interactive connection with lftp
 
 For interactive sessions, use `lftp` with the following command:
-```sh
+```bash
 apt install lftp  # Requirement
 
 FTP_HOST="ftp://dedibackup-dc3.online.net"
@@ -147,7 +147,7 @@ EOF
 #### Example of automated connection with curl
 When automating tasks, you can use `curl`, though command limitations may apply:
 
-```sh
+```bash
 # Upload a file
 curl -T "path_to_your_file.7z" -u "sd-XXXXX:your_password" ftp://dedibackup-dc3.online.net/
 ```

pages/edge-services/reference-content/ssl-tls-certificate.mdx

@@ -122,7 +122,7 @@ openssl x509 -in cert.cer -out cert.pem
 
 When you have your key, your server certificate and your root certificate all in separate files, you can use the `cat` command to chain them together into one file, ready to be copied and pasted:
 
-```sh
+```bash
 cat private_key.pem cert.pem root_cert.pem > cert_chain.pem
 ```
 

pages/elastic-metal/api-cli/elastic-metal-with-api.mdx

@@ -31,13 +31,13 @@ Besides creating your Elastic Metal servers from the graphical [Scaleway console
 </Message>
 
 1. Open a terminal on your computer and set your secret API key, your SSH key ID, and your Project ID as variables.
-    ```sh
+    ```bash
     export SCW_SECRET_KEY="<Your secret key>"
     export SCW_SSH_KEY="<Your SSH key ID>"
     export SCW_PROJECT_ID="<Your Project ID>"
     ```
 2. Retrieve a list of all operating systems available in the desired Availability Zone.
-    ```sh
+    ```bash
     curl https://api.scaleway.com/baremetal/v1/zones/fr-par-2/offers -H "X-Auth-Token: $SCW_SECRET_KEY" | jq . | grep "EM-"
     ```
 
@@ -157,7 +157,7 @@ Besides creating your Elastic Metal servers from the graphical [Scaleway console
     }
     ```
 5. The server is being delivered to your account and is automatically being installed on the operating system chosen. You can retrieve the status of the installation using the following API call:
-    ```sh
+    ```bash
     curl https://api.scaleway.com/baremetal/v1/zones/fr-par-2/servers/{server_id} -H "X-Auth-Token: $SCW_SECRET_KEY" | jq .
     ```