Skip to content

Commit 3547994

Browse files
authored
fix(tutos): fix tutos (#4966)
1 parent e57cb80 commit 3547994

File tree

10 files changed

+21
-94
lines changed

10 files changed

+21
-94
lines changed

tutorials/systemd-essentials/index.mdx

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
meta:
33
title: Learning systemd essentials
4-
description: This page shows how to manage units on your server with systemd.
4+
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.
55
content:
66
h1: Learning systemd essentials
7-
paragraph: This page shows how to manage units on your server with systemd.
7+
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.
88
tags: systemd instances
99
categories:
1010
- instances
@@ -87,7 +87,7 @@ systemctl list-unit-files
8787

8888
## Using units
8989

90-
The most common object that `systemd` manages and acts upon is a "`unit`".
90+
The most common object that `systemd` manages and acts upon is a `unit`.
9191
Units can be, for example, services (.service), devices (.device), mount points (.mount), or sockets (.socket).
9292

9393
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:
157157
systemctl disable unit
158158
```
159159

160-
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.)_:
160+
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
161+
162+
<Message type="important">
163+
This makes it impossible to start the concerned service either manually or as a dependency. Use it carefully.
164+
</Message>
161165

162166
```s
163167
systemctl mask unit
@@ -185,7 +189,7 @@ To shut down and **reboot** the system, type:
185189
systemctl reboot
186190
```
187191

188-
To shut down and **power-off** the system, run the following command:
192+
To shut down and **power off** the system, run the following command:
189193

190194
```s
191195
systemctl poweroff
@@ -272,10 +276,10 @@ journalctl -u unit
272276

273277
## Exploring units and unit files
274278

275-
To explore the content of a Unit File, some options are available.
276-
A Unit File contains the parameters that are used by systemd to manage and run a unit.
279+
To explore the content of a unit file, some options are available.
280+
A unit file contains the parameters that are used by systemd to manage and run a unit.
277281

278-
To see the full content of a Unit file, type:
282+
To see the full content of a unit file, type:
279283

280284
```s
281285
systemctl cat unit
@@ -299,13 +303,13 @@ This command will give you a list in return, showing each parameter being manage
299303

300304
Systemctl allows you to edit unit files directly from the application, without needing to know the exact location of the file on the disk.
301305

302-
To add a snippet to an existing unit file, which can be used to append or overwrite configurations in the default Unit File, type:
306+
To add a snippet to an existing unit file, which can be used to append or overwrite configurations in the default unit file, type:
303307

304308
```s
305309
systemctl edit unit
306310
```
307311

308-
It is also possible to modify the entire content of the Unit File instead of creating a snippet by using the `--full` flag:
312+
It is also possible to modify the entire content of the unit file instead of creating a snippet by using the `--full` flag:
309313

310314
```s
311315
systemctl edit --full unit
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
-148 KB
Binary file not shown.

tutorials/trigger-ifttt-actions/index.mdx

Lines changed: 0 additions & 79 deletions
This file was deleted.

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

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ categories:
1010
- instances
1111
tags: Private-Network instances Public-Gateway
1212
dates:
13-
validation: 2024-11-05
13+
validation: 2025-05-14
1414
---
1515

1616
## Private Networks and Public Gateways - Overview
@@ -47,7 +47,7 @@ dates:
4747
valid_lft forever preferred_lft forever
4848
```
4949
3. Go to the [VPC page](https://console.scaleway.com/vpc/vpc) of the Scaleway console.
50-
4. Click the default VPC of the region that covers your Instance's Availability Zone.
50+
4. Click a VPC of the region that covers your Instance's Availability Zone.
5151
5. Click **Create Private Network**. The Private Network creation wizard displays:
5252
<Lightbox src="scaleway-vpc-create-pn.webp" alt="" />
5353
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
113113

114114
* [VPC Quickstart](/public-gateways/quickstart/)
115115
* [How to use Private Networks](/instances/how-to/use-private-networks/)
116-
* [How to configure a Public Gateway](/public-gateways/how-to/configure-a-public-gateway/)
116+
* [How to configure a Public Gateway](/public-gateways/how-to/configure-a-public-gateway/)
117+
* [Getting the most from your Private Networks](/vpc/reference-content/getting-most-private-networks/)
118+
* [Creating a basic infrastructure to leverage VPC isolation](/vpc/reference-content/use-case-basic/)

tutorials/zabbix-monitoring/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
meta:
33
title: Monitoring Instances with Zabbix on Ubuntu Jammy Jellyfish (22.04 LTS)
4-
description: Zabbix is an open-source monitoring solution for devices and services
4+
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.
55
content:
66
h1: Monitoring Instances with Zabbix on Ubuntu Jammy Jellyfish (22.04 LTS)
7-
paragraph: Zabbix is an open-source monitoring solution for devices and services
7+
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.
88
tags: instances Zabbix monitoring MariaDB
99
categories:
1010
- instances

0 commit comments

Comments
 (0)