fix(tutos): fix tutos

tutorials/systemd-essentials/index.mdx

@@ -1,10 +1,10 @@
 ---
 meta:
   title: Learning systemd essentials
-  description: This page shows how to manage units on your server with systemd.
+  description: Learn the essentials of systemd, a core component of Linux systems, and master its usage with our in-depth tutorial, covering key concepts and practical examples.
 content:
   h1: Learning systemd essentials
-  paragraph: This page shows how to manage units on your server with systemd.
+  paragraph: Learn the essentials of systemd, a core component of Linux systems, and master its usage with our in-depth tutorial, covering key concepts and practical examples.
 tags: systemd instances
 categories:
   - instances
@@ -87,7 +87,7 @@ systemctl list-unit-files
 
 ## Using units
 
-The most common object that `systemd` manages and acts upon is a "`unit`".
+The most common object that `systemd` manages and acts upon is a `unit`.
 Units can be, for example, services (.service), devices (.device), mount points (.mount), or sockets (.socket).
 
 You should always specify the complete name of the unit file, including its suffix (for example sshd.socket). A short form is available for .service files. For example `nginx` is equivalent to `nginx.service`.
@@ -157,7 +157,11 @@ To **disable** a unit to not start during bootup:
 systemctl disable unit
 ```
 
-Every service unit that is known to systemd may be started manually – even if it is disabled. To explicitly keep a service from running, use the **mask** command _(Attention: This makes it impossible to start the concerned service. Neither manually nor as a dependency. Use it carefully.)_:
+Every service unit that is known to systemd may be started manually – even if it is disabled. To explicitly keep a service from running, use the **mask** command
+
+<Message type="important">
+This makes it impossible to start the concerned service either manually or as a dependency. Use it carefully.
+</Message>
 
 ```s
 systemctl mask unit
@@ -185,7 +189,7 @@ To shut down and **reboot** the system, type:
 systemctl reboot
 ```
 
-To shut down and **power-off** the system, run the following command:
+To shut down and **power off** the system, run the following command:
 
 ```s
 systemctl poweroff
@@ -272,10 +276,10 @@ journalctl -u unit
 
 ## Exploring units and unit files
 
-To explore the content of a Unit File, some options are available.
-A Unit File contains the parameters that are used by systemd to manage and run a unit.
+To explore the content of a unit file, some options are available.
+A unit file contains the parameters that are used by systemd to manage and run a unit.
 
-To see the full content of a Unit file, type:
+To see the full content of a unit file, type:
 
 ```s
 systemctl cat unit
@@ -299,13 +303,13 @@ This command will give you a list in return, showing each parameter being manage
 
 Systemctl allows you to edit unit files directly from the application, without needing to know the exact location of the file on the disk.
 
-To add a snippet to an existing unit file, which can be used to append or overwrite configurations in the default Unit File, type:
+To add a snippet to an existing unit file, which can be used to append or overwrite configurations in the default unit file, type:
 
 ```s
 systemctl edit unit
 ```
 
-It is also possible to modify the entire content of the Unit File instead of creating a snippet by using the `--full` flag:
+It is also possible to modify the entire content of the unit file instead of creating a snippet by using the `--full` flag:
 
 ```s
 systemctl edit --full unit

tutorials/vpc-public-gateway-autoconfiguration/index.mdx

@@ -10,7 +10,7 @@ categories:
   - instances
 tags: Private-Network instances Public-Gateway
 dates:
-  validation: 2024-11-05
+  validation: 2025-05-14
 ---
 
 ## Private Networks and Public Gateways - Overview
@@ -47,7 +47,7 @@ dates:
         valid_lft forever preferred_lft forever
     ```
 3. Go to the [VPC page](https://console.scaleway.com/vpc/vpc) of the Scaleway console.
-4. Click the default VPC of the region that covers your Instance's Availability Zone.
+4. Click a VPC of the region that covers your Instance's Availability Zone.
 5. Click **Create Private Network**. The Private Network creation wizard displays:
     <Lightbox src="scaleway-vpc-create-pn.webp" alt="" />
 6. Leave the default settings in place, or enter a customized **name**, **tags** and, in **Advanced Settings**, **CIDR block**.
@@ -113,4 +113,6 @@ Congratulations, you have completed your first configuration of Instances in a P
 
 * [VPC Quickstart](/public-gateways/quickstart/)
 * [How to use Private Networks](/instances/how-to/use-private-networks/)
-* [How to configure a Public Gateway](/public-gateways/how-to/configure-a-public-gateway/)
+* [How to configure a Public Gateway](/public-gateways/how-to/configure-a-public-gateway/)
+* [Getting the most from your Private Networks](/vpc/reference-content/getting-most-private-networks/)
+* [Creating a basic infrastructure to leverage VPC isolation](/vpc/reference-content/use-case-basic/)

tutorials/zabbix-monitoring/index.mdx

@@ -1,10 +1,10 @@
 ---
 meta:
   title: Monitoring Instances with Zabbix on Ubuntu Jammy Jellyfish (22.04 LTS)
-  description: Zabbix is an open-source monitoring solution for devices and services
+  description: Learn how to set up Zabbix monitoring on Scaleway with our step-by-step tutorial. Discover how to efficiently monitor your infrastructure and applications with this comprehensive guide.
 content:
   h1: Monitoring Instances with Zabbix on Ubuntu Jammy Jellyfish (22.04 LTS)
-  paragraph: Zabbix is an open-source monitoring solution for devices and services
+  paragraph: Learn how to set up Zabbix monitoring on Scaleway with our step-by-step tutorial. Discover how to efficiently monitor your infrastructure and applications with this comprehensive guide.
 tags: instances Zabbix monitoring MariaDB
 categories:
   - instances