chore(gen): doc review MTA-5351 (scaleway#4097)

SamyOubouaziz · Laure-di · commit 56a45902c245 · 2025-02-27T11:14:34.000+01:00
* chore(gen): doc review MTA-5351

* chore(gen): update

* chore(gen): update

* chore(gen): update

* chore(gen): update

* chore(gen): update

* chore(gen): update

* chore(gen): update

* chore(gen): update

* chore(gen): update
diff --git a/serverless/sql-databases/api-cli/secure-connection-ssl-tls.mdx b/serverless/sql-databases/api-cli/secure-connection-ssl-tls.mdx
@@ -6,7 +6,7 @@ content:
   h1: Secure connections using SSL/TLS
   paragraph: Guide to securing your serverless SQL database connections using SSL/TLS protocols.
 dates:
-  validation: 2024-06-03
+  validation: 2024-12-09
   posted: 2024-06-03
 ---
 
diff --git a/storage/object/troubleshooting/cannot-access-data.mdx b/storage/object/troubleshooting/cannot-access-data.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Troubleshoot issues related to accessing data in Scaleway Object Storage.
 tags: help troubleshooting object storage blocked data locked fail unable impossible
 dates:
-  validation: 2024-06-04
+  validation: 2024-12-09
   posted: 2024-06-04
 categories:
   - storage
diff --git a/storage/object/troubleshooting/cannot-delete-bucket.mdx b/storage/object/troubleshooting/cannot-delete-bucket.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Guide to solving bucket deletion problems in Object Storage.
 tags: help troubleshooting object storage delete bucket fail unable impossible
 dates:
-  validation: 2024-06-04
+  validation: 2024-12-09
   posted: 2024-06-04
 categories:
   - storage
diff --git a/storage/object/troubleshooting/cannot-restore-glacier.mdx b/storage/object/troubleshooting/cannot-restore-glacier.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn to troubleshoot issues when restoring Glacier objects.
 tags: help troubleshooting object storage restore glacier fail unable impossible
 dates:
-  validation: 2024-06-04
+  validation: 2024-12-09
   posted: 2024-06-04
 categories:
   - storage
@@ -20,11 +20,11 @@ categories:
 
 ## Problem
 
-I need to retrieve my data from Scaleway Glacier, but the restore operation does not seem to function.
+I need to retrieve my data from Scaleway Glacier, but the restore operation does not seem to work.
 
 ## Cause
 
-The time it takes to restore an object depends on the size of the object and if [multipart](/storage/object/concepts/#multipart-uploads) is configured. If your object is larger than 1 MB, it can take anywhere from a few minutes to 24 hours for restore to start.
+The time it takes to restore an object depends on the size of the object, and if [multipart](/storage/object/concepts/#multipart-uploads) is configured. If your object is larger than 1 MB, it can take anywhere from a few minutes to 24 hours for restore to start.
 
 ## Solution
  
diff --git a/storage/object/troubleshooting/low-performance.mdx b/storage/object/troubleshooting/low-performance.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Diagnose and improve Object Storage performance.
 tags: help troubleshooting object storage poor performance issues slow
 dates:
-  validation: 2024-06-04
+  validation: 2024-12-09
   posted: 2024-06-04
 categories:
   - storage
diff --git a/tutorials/install-parse-server/index.mdx b/tutorials/install-parse-server/index.mdx
@@ -10,7 +10,7 @@ categories:
   - instances
 hero: assets/scaleway_parse.webp
 dates:
-  validation: 2024-06-03
+  validation: 2024-12-13
   posted: 2020-11-03
 ---
 
diff --git a/tutorials/install-pgbouncer/index.mdx b/tutorials/install-pgbouncer/index.mdx
@@ -10,11 +10,11 @@ categories:
   - instances
   - postgresql-and-mysql
 dates:
-  validation: 2024-06-03
+  validation: 2024-12-12
   posted: 2022-02-24
 ---
 
-PgBouncer is a connection pooler for PostgreSQL. It sits between the application and the PostgreSQL server. PgBouncer opens multiple connections to the database and serves it to the application. This reduces connection opening costs for the application and gives a performance boost.
+[PgBouncer](https://www.pgbouncer.org/) is a connection pooler for [PostgreSQL](https://www.postgresql.org/). It sits between the application and the PostgreSQL server. PgBouncer opens multiple connections to the database and serves it to the application. This reduces connection opening costs for the application and gives a performance boost.
 
 There are three types of pooling modes:
 - Session: The server connection will be released back to the pool after the client disconnects. (Default pooling method.)
@@ -35,7 +35,7 @@ In this tutorial, you can choose the pooling mode that best suits your workload.
 
 The **PostgreSQL Global Development Group (PGDG)** provides an apt repository. After importing the repository, you can install the PgBouncer package.
 
-1. Import the PDGG repository signing key:
+1. Import the PGDG repository signing key:
     ```
     sudo apt install curl ca-certificates
     sudo install -d /usr/share/postgresql-common/pgdg
@@ -133,7 +133,7 @@ Here are a few commands that can be used after connecting to the `pgbouncer` dat
 
 ## Doing an online restart
 
-- You can do an online restart without terminating the connections. PgBouncer launches a new process and loads open sockets from running PgBouncer. After that, the old process is stopped and the new process resumes. This way, connections are not interrupted. This is very useful when upgrading PgBouncer.
+You can do an online restart without terminating the connections. PgBouncer launches a new process and loads open sockets from running PgBouncer. After that, the old process is stopped and the new process resumes. This way, connections are not interrupted. This is very useful when upgrading PgBouncer.
     ```
     sudo -u postgres pgbouncer -R /etc/pgbouncer/pgbouncer.ini -d
     ```
@@ -150,17 +150,17 @@ Here are a few commands that can be used after connecting to the `pgbouncer` dat
     max_client_conn = max_client_conn + (max pool_size * total databases * total users)
     ```
 
-- You may want to increase this number to 5 or 10. When the specified `pool_size` is not enough, it uses the reserved pool and logs it. It can be used to determine `pool_size`. (Default: 0)
+- You can set this value to 5 or 10. When the specified `pool_size` is not enough, it uses the reserved pool and logs it. It can be used to determine `pool_size`. (Default: 0)
     ```
     reserve_pool_size = 10
     ```
 
-- Connecting to PostgreSQL through PgBouncer will mask the PostgreSQL IP. This setting adds the client host address and port to the application name. It is very helpful when troubleshooting. (Default: 0)
+- Connecting to PostgreSQL through PgBouncer will mask the PostgreSQL IP. This setting adds the client host address and port to the application name, which can be helpful when troubleshooting. (Default: 0)
     ```
     application_name_add_host = 1
     ```
 
-- By default, PgBouncer reuses server connections in LIFO (last-in, first-out). If you are using a TCP load balancer with a round-robin behind the PostgreSQL IP address, you may want to enable `server_round_robin` to achieve higher performance. (Default: 1)
+- By default, PgBouncer reuses server connections in LIFO (last-in, first-out). If you are using a TCP load balancer with a round-robin behind the PostgreSQL IP address, enable `server_round_robin` to achieve higher performance. (Default: 1)
     ```
     server_round_robin = 1
     ```
diff --git a/tutorials/installation-lemp-ubuntu-bionic/index.mdx b/tutorials/installation-lemp-ubuntu-bionic/index.mdx
@@ -15,7 +15,7 @@ dates:
 
 The LEMP-Stack references a group of software that can be used to serve dynamic web applications and websites. **LEMP** is an acronym and stands for:
 
-- A Linux operating system
+- A [Linux](https://www.linux.org/) operating system
 - A [Nginx](http://nginx.org/) (pronounced as _Engine-X_) web server
 - A [MySQL](https://www.mysql.com/) (or [MariaDB](https://mariadb.org/), which is a drop-in fork of MySQL) database server
 - [PHP](http://www.php.net/) for dynamic data processing
diff --git a/tutorials/installation-uncomplicated-firewall/index.mdx b/tutorials/installation-uncomplicated-firewall/index.mdx
@@ -9,7 +9,7 @@ tags: Firewall UFW port-25
 categories:
   - instances
 dates:
-  validation: 2024-06-03
+  validation: 2024-12-13
   posted: 2018-07-18
 ---
 
@@ -21,12 +21,24 @@ UFW, or **[Uncomplicated FireWall](https://en.wikipedia.org/wiki/Uncomplicated_F
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa or later
 - An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/)
 - `sudo` privileges or access to the root user
 
 ## Installing UFW
 
-UFW is available as a pre-built package in the apt repositories of Ubuntu. It can be easily installed via apt:
+UFW is available as a pre-built package in the apt repositories of Ubuntu. It can be easily installed via `apt`.
+
+1. Connect to your Instance with SSH. In a terminal run:
+    ```
+    ssh root@<your_instance_ip>
+    ```
+2. Update the system and upgrade the software already installed on the Instance.
+    ```
+    apt update && apt upgrade -y
+    ```
+
+3. run the command below to install UFW:
 
   ```code
   sudo apt-get install ufw
@@ -82,7 +94,7 @@ The services running on the machine used in this example need the following port
     ```
 
     <Message type="note">
-      In this case `TCP` has not to be specified, as both, `TCP` and `UDP` are needed.
+      In this case `TCP` has not to be specified, as both `TCP` and `UDP` are needed.
     </Message>
 5. Activate the new rules.
     ```code
@@ -130,7 +142,8 @@ Over time, you may recognize that some of the rules you defined previously do no
     ```
 
   The numbers at the beginning of each row are the number of the rule in UFW.
+
 2. To delete a rule, find its number and type:
     ```code
-    sudo ufw delete NUMBER
+    sudo ufw delete <RULE_NUMBER>
     ```
diff --git a/tutorials/jitsi-ubuntu-jammy-jellyfish/index.mdx b/tutorials/jitsi-ubuntu-jammy-jellyfish/index.mdx
@@ -10,7 +10,7 @@ categories:
   - domains-and-dns
 tags: media videoconferencing Jitsi-Meet
 dates:
-  validation: 2024-06-03
+  validation: 2024-12-12
   posted: 2022-11-16
 ---
 
@@ -80,13 +80,13 @@ Jitsi Meet provides users with a complete suite of tools, making virtual meeting
 
     When asked:
 
-    - Enter the FQDN of your Instance. For example `jitsi.mydomain.tld` and press **Enter**.
+    - Enter the [FQDN](/network/domains-and-dns/concepts/#fully-qualified-domain-name-fqdn) of your Instance (for example `jitsi.mydomain.tld`), and press **Enter**.
     - Choose the `Let's Encrypt certificates` option as an SSL certificate and press **Enter**.
     - Enter your email address.
     - Enter your phone number (optional).
 7. Open a web browser and type the FQDN of your Instance, for example: `https://jitsi.mydomain.tld`. The following screen displays:
     <Lightbox src="scaleway-jitsi_home.webp" alt="" />
-8. Enter a name for your conference and press `Start meeting` to enter the conference room.
+8. Enter a name for your conference, and press `Start meeting` to enter the conference room.
     <Lightbox src="scaleway-jitsi-meet-conf-call.webp" alt="" />
 
 For more information about Jitsi Meet and the advanced configuration of the tool, refer to the [official Jitsi documentation](https://jitsi.github.io/handbook/docs/intro/).
diff --git a/tutorials/restic-s3-backup/index.mdx b/tutorials/restic-s3-backup/index.mdx
@@ -11,7 +11,7 @@ categories:
   - instances
   - object-storage
 dates:
-  validation: 2024-06-03
+  validation: 2024-12-13
   posted: 2022-04-04
 ---
 
@@ -52,7 +52,7 @@ In this tutorial, you learn how to backup a Scaleway Instance running on Ubuntu
 
 A repository is the storage space where your backups will be hosted. In this tutorial, we will use Scaleway Object Storage buckets to host our backups.
 
-1. Set up your [environment variables](https://github.com/scaleway/scaleway-sdk-go/tree/master/scw#environment-variables), if you have not done so yet. Replace `$SCW_ACCESS_KEY` and `$SCW_SECRET_KEY` with their corresponding values.
+1. Set up your [environment variables](/developer-tools/scaleway-cli/reference-content/environment-variables/), if you have not done so yet. Replace `$SCW_ACCESS_KEY` and `$SCW_SECRET_KEY` with their corresponding values.
     ```
     export AWS_ACCESS_KEY_ID=$SCW_ACCESS_KEY
     export AWS_SECRET_ACCESS_KEY=$SCW_SECRET_KEY
@@ -71,7 +71,7 @@ A repository is the storage space where your backups will be hosted. In this tut
     </Message>
 
     <Message type="tip">
-      Restic requests you to enter the password every time you perform actions on your repository. If you have configured automatic backups, you might want to set up an [environment variable](https://restic.readthedocs.io/en/latest/040_backup.html#environment-variables) for your password.
+      Restic requests you to enter the password every time you perform actions on your repository. If you have configured automatic backups, you can set up an [environment variable](https://restic.readthedocs.io/en/latest/040_backup.html#environment-variables) for your password.
     </Message>
 
 An output displays, informing the name and path of your repository.
@@ -82,15 +82,18 @@ created restic repository da8e38a165 at s3:https://s3.fr-par.scw.cloud/<bucket_n
 
 ## Creating backups
 
-1. Run the command below to create a backup. Include the path to your repository (in this example, the path is the endpoint of your bucket), and the path of the directory you wish to back up (`~/<my-directory>` in the example).
+1. Run the command below to create a backup. Include the path to your repository (in this example, the path is the endpoint of your bucket), and the path of the directory you want to back up (`~/<my-directory>` in the example).
     ```
     restic -r s3:https://s3.fr-par.scw.cloud/<bucket_name> backup ~/<my-directory>
     ```
 
     The command above creates a snapshot of your directory and sends it to your repository. The snapshot is stored as an object in your bucket.
 
     <Message type="tip">
-      By default, the backups you create are stored using `STANDARD` [storage class](/storage/object/concepts/#storage-class). If you want to use a different storage class, you can add the `-o s3.storage-class=<STORAGE_CLASS>` option to your command. For example: `restic -r s3:https://s3.fr-par.scw.cloud/<bucket_name> backup -o s3.storage-class=ONEZONE_IA ~/<my-directory>`
+      By default, the backups you create are stored using `STANDARD` [storage class](/storage/object/concepts/#storage-class). If you want to use a different storage class, you can add the `-o s3.storage-class=<STORAGE_CLASS>` option to your command, as shown below:
+      ```
+      restic -r s3:https://s3.fr-par.scw.cloud/<bucket_name> backup -o s3.storage-class=ONEZONE_IA ~/<my-directory>
+      ```
     </Message>
 2. Enter the password for the repository when prompted.
     ```
@@ -141,7 +144,7 @@ created restic repository da8e38a165 at s3:https://s3.fr-par.scw.cloud/<bucket_n
     restic -r s3:https://s3.fr-par.scw.cloud/<bucket_name> restore 15a39fd5 --target ~/<my-directory>
     ```
 
-    If the operation is successful, you see the following output:
+    If the operation is successful, the following output displays:
 
     ```
     enter password for repository:
diff --git a/tutorials/sem-terraform/index.mdx b/tutorials/sem-terraform/index.mdx
@@ -11,11 +11,11 @@ categories:
   - secret-manager
   - managed-databases
 dates:
-  validation: 2024-06-03
+  validation: 2024-12-13
   posted: 2024-06-03
 ---
 
-In this tutorial, you will use a Terraform configuration file that builds your entire infrastructure such as a [Database Instance](/managed-databases/postgresql-and-mysql/concepts/#database-instance), a [secret](/identity-and-access-management/secret-manager/concepts/#secret) and a [version](/identity-and-access-management/secret-manager/concepts/#version) in which your database credentials are stored. You will then be able to access your database credentials securely from the Scaleway console.
+In this tutorial, you will use a Terraform configuration file that builds your entire infrastructure, such as a [Database Instance](/managed-databases/postgresql-and-mysql/concepts/#database-instance), a [secret](/identity-and-access-management/secret-manager/concepts/#secret), and a [version](/identity-and-access-management/secret-manager/concepts/#version) in which your database credentials are stored. You will then be able to access your database credentials securely from the Scaleway console.
 
 <Macro id="requirements" />
 
@@ -49,7 +49,19 @@ The Scaleway [GitHub repository](https://github.com/scaleway/tutorial-sem-terraf
     ```
 ### Understanding the files and directories
 
-In the `tutorial-sem-terraform` directory, you will find a folder named `examples` which contains the `key-value` folder. The `key-value` folder contains two additional folders named `app` and `infra`. The `infra` folder contains the files that will configure your database and secret, whereas the `app` folder will interact with the database and ask [Secret Manager](/identity-and-access-management/secret-manager/concepts/#secret-manager) for the password to connect to the database.
+In the `tutorial-sem-terraform` repository, you will find the following folder structure:
+
+```
+examples/
+├─ key-value/
+   ├─ app/
+   ├─ infra/
+
+```
+
+- The `key-value` folder contains two additional folders named `app` and `infra`.
+- The `app` folder will interact with the database and ask [Secret Manager](/identity-and-access-management/secret-manager/concepts/#secret-manager) for the password to connect to the database.
+- The `infra` folder contains the files that will configure your database and secret.
 
 ## Build and deploy your infrastructure
 
