Skip to content

Commit 4ea5bf8

Browse files
committed
fix(gen): fix false positives
1 parent d833748 commit 4ea5bf8

File tree

41 files changed

+56
-56
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

41 files changed

+56
-56
lines changed

pages/dedibox-kvm-over-ip/concepts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ KVM Over IP is a hardware-based solution that enables remote access to the **k**
1212

1313
## iDRAC
1414

15-
The **I**ntegrated **D**ell **R**emote **A**ccess **C**controller is the hardware allowing KVM Over IP and other management and monitoring features for Dell servers.
15+
The **I**ntegrated **D**ell **R**emote **A**ccess **C**ontroller is the hardware allowing KVM Over IP and other management and monitoring features for Dell servers.
1616

1717
## iLO card
1818

pages/dedibox-kvm-over-ip/how-to/understanding-bmc.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ A **Baseboard Management Controller (BMC)** is a specialized microcontroller emb
1212
Different server vendors provide proprietary BMC implementations with similar functionality, including:
1313
- IPMI (Intelligent Platform Management Interface): A standardized protocol for BMC communication.
1414
- Dell iDRAC (Integrated Dell Remote Access Controller)
15-
- HOPE iLO (Integrated Lights-Out)
15+
- HPE iLO (Integrated Lights-Out)
1616
- Supermicro IPMI
1717
- Quanta IPMI
1818

pages/dedibox-kvm-over-ip/quickstart.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ import image from './assets/scaleway-idrac.webp'
1111
import image2 from './assets/scaleway-ilo.webp'
1212

1313

14-
An **I**ntelligent **P**latform **M**anagement **I**nterface (IPMI) is an industry standard to describe the subsystem of a server providing remote management and monitoring capabilities. IPMI allows you to manage and monitor a server even if it is powered off or unresponsive, by using a network connection to the hardware. IPMI is made possible by the **B**aseboard **M**anagement **C**controller, an independent piece of hardware connected to your network card, composed of an I2C bus and a dedicated processor.
14+
An **I**ntelligent **P**latform **M**anagement **I**nterface (IPMI) is an industry standard to describe the subsystem of a server providing remote management and monitoring capabilities. IPMI allows you to manage and monitor a server even if it is powered off or unresponsive, by using a network connection to the hardware. IPMI is made possible by the **B**aseboard **M**anagement **C**ontroller, an independent piece of hardware connected to your network card, composed of an I2C bus and a dedicated processor.
1515

1616
Some examples of features that can be remotely monitored via the IPMI include:
1717

@@ -37,7 +37,7 @@ In this document, we show you how to access the IPMI for a Dell or HP server. Se
3737

3838
## How to use IPMI via Dell iDRAC
3939

40-
IPMI is a standard specification for a remote management subsystem. On a Dell server, IPMI is realized through the iDRAC: the **I**ntegrated **D**ell **R**emote **A**ccess **C**controller.
40+
IPMI is a standard specification for a remote management subsystem. On a Dell server, IPMI is realized through the iDRAC: the **I**ntegrated **D**ell **R**emote **A**ccess **C**ontroller.
4141

4242
1. From the console, click **Server** > **Server list**. A list of your servers displays.
4343
2. Click **Manage** next to the relevant server.
@@ -56,9 +56,9 @@ IPMI is a standard specification for a remote management subsystem. On a Dell se
5656
- The **iDDRAC** tabs show you information about the iDRAC itself.
5757
- Click the other relevant links on the left sidebar to see information about **Batteries**, **Temperatures**, **Voltages** etc., as required.
5858

59-
## How to use IPMI via HOPE iLO
59+
## How to use IPMI via HPE iLO
6060

61-
IPMI is a standard specification for a remote management subsystem. On an HOPE server, IPMI is realized through the ILO: the **I**ntegrated **L**ights **O**ut processor.
61+
IPMI is a standard specification for a remote management subsystem. On an HPE server, IPMI is realized through the ILO: the **I**ntegrated **L**ights **O**ut processor.
6262

6363
1. From the console, click **Server** > **Server list**. A list of your servers displays.
6464
2. Click **Manage** next to the relevant server.

pages/dedibox/how-to/use-ipmi-on-server.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ import image from './assets/scaleway-idrac.webp'
1212
import image2 from './assets/scaleway-ilo.webp'
1313

1414

15-
An **I**ntelligent **P**latform **M**anagement **I**nterface (IPMI) is an industry standard to describe the subsystem of a server providing remote management and monitoring capabilities. IPMI gives you a way to manage and monitor a server even if it is powered off or unresponsive, by using a network connection to the hardware. IPMI is made possible by the **B**aseboard **M**anagement **C**controller, an independent piece of hardware connected to your network card, composed of an I2C bus and a dedicated processor.
15+
An **I**ntelligent **P**latform **M**anagement **I**nterface (IPMI) is an industry standard to describe the subsystem of a server providing remote management and monitoring capabilities. IPMI gives you a way to manage and monitor a server even if it is powered off or unresponsive, by using a network connection to the hardware. IPMI is made possible by the **B**aseboard **M**anagement **C**ontroller, an independent piece of hardware connected to your network card, composed of an I2C bus and a dedicated processor.
1616

1717
Some examples of features that can be remotely monitored via the IPMI include:
1818

@@ -38,7 +38,7 @@ In this document, we show you how to access the IPMI for a Dell or HP server. Se
3838

3939
## How to use IPMI via Dell iDRAC
4040

41-
IPMI is a standard specification for a remote management subsystem. On a Dell server, IPMI is realized through the iDRAC: the **I**ntegrated **D**ell **R**emote **A**ccess **C**controller.
41+
IPMI is a standard specification for a remote management subsystem. On a Dell server, IPMI is realized through the iDRAC: the **I**ntegrated **D**ell **R**emote **A**ccess **C**ontroller.
4242

4343
1. From the console, click **Server** > **Server list**. A list of your servers displays.
4444
2. Click **Manage** next to the relevant server.

pages/edge-services/concepts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,4 +79,4 @@ The protocol (HTTP or HTTPS) that the Edge Services pipeline should use when sen
7979

8080
## WAF
8181

82-
An Edge Services **W**eb **A**application **F**irewall (WAF) evaluates requests to your origin to determine whether they are potentially malicious. You can set the [paranoia level](#paranoia-level) to be used when evaluating requests. Requests that are judged to be malicious are then blocked or logged, depending on the settings you choose. Find out more about [configuring a WAF](/edge-services/how-to/configure-waf/).
82+
An Edge Services **W**eb **A**pplication **F**irewall (WAF) evaluates requests to your origin to determine whether they are potentially malicious. You can set the [paranoia level](#paranoia-level) to be used when evaluating requests. Requests that are judged to be malicious are then blocked or logged, depending on the settings you choose. Find out more about [configuring a WAF](/edge-services/how-to/configure-waf/).

pages/edge-services/faq.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Edge Services is a feature for Scaleway Load Balancers and Object Storage bucket
2222

2323
### What is WAF?
2424

25-
**W**eb **A**application **F**irewall is a feature available via Edge Services. When enabled, WAF filters requests to your origin to determine whether they are potentially malicious. You can choose the [paranoia level](/edge-services/concepts/#paranoia-level) to be used when evaluating requests, and set [exclusions](/edge-services/concepts/#exclusions) to define traffic that should not be filtered by WAF. Requests that are judged to be malicious are blocked or logged, depending on the settings you choose. Find out more about WAF in our [detailed documentation](/edge-services/reference-content/understanding-waf/).
25+
**W**eb **A**pplication **F**irewall is a feature available via Edge Services. When enabled, WAF filters requests to your origin to determine whether they are potentially malicious. You can choose the [paranoia level](/edge-services/concepts/#paranoia-level) to be used when evaluating requests, and set [exclusions](/edge-services/concepts/#exclusions) to define traffic that should not be filtered by WAF. Requests that are judged to be malicious are blocked or logged, depending on the settings you choose. Find out more about WAF in our [detailed documentation](/edge-services/reference-content/understanding-waf/).
2626

2727
## Pricing and billing
2828

pages/edge-services/how-to/configure-waf.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ import image2 from './assets/scaleway-edge-waf-popup.webp'
1313
import image3 from './assets/scaleway-edge-waf-add-exc.webp'
1414

1515

16-
An Edge Services **W**eb **A**application **F**irewall (WAF) evaluates requests to your Load Balancer origin to determine whether they are potentially malicious. You can choose the [paranoia level](/edge-services/concepts/#paranoia-level) to be used when evaluating requests, and set [exclusions](/edge-services/concepts/#exclusions) to define traffic that shouldn't be filtered by WAF. Requests that are judged to be malicious are blocked or logged, depending on the settings you choose.
16+
An Edge Services **W**eb **A**pplication **F**irewall (WAF) evaluates requests to your Load Balancer origin to determine whether they are potentially malicious. You can choose the [paranoia level](/edge-services/concepts/#paranoia-level) to be used when evaluating requests, and set [exclusions](/edge-services/concepts/#exclusions) to define traffic that shouldn't be filtered by WAF. Requests that are judged to be malicious are blocked or logged, depending on the settings you choose.
1717

1818
This page walks you through the process of enabling and configuring WAF to protect your Load Balancer origin.
1919

pages/edge-services/how-to/create-pipeline-lb.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ You can create an Edge Services pipeline from the Load Balancer section of the c
5353

5454
6. Optionally, configure **Advanced Settings:**
5555
- **Cache**: When enabled, content from your Load Balancer origin is cached with Edge Services and served directly to users from Edge Services' servers. Set a **Lifetime** value, in seconds, to dictate how long objects should remain in the cache before being freshly retrieved from the origin. [Find out more about caching](/edge-services/how-to/configure-cache/).
56-
- **WAF**: When enabled, requests to your Load Balancer origin are evaluated by a **W**eb **A**application **F**irewall. Malicious requests are blocked or logged, depending on your settings. Set a paranoia level to determine WAF's aggressivity, and a mode (block or log) for dealing with malicious requests. [Find out more about WAF](/edge-services/reference-content/understanding-waf/).
56+
- **WAF**: When enabled, requests to your Load Balancer origin are evaluated by a **W**eb **A**pplication **F**irewall. Malicious requests are blocked or logged, depending on your settings. Set a paranoia level to determine WAF's aggressivity, and a mode (block or log) for dealing with malicious requests. [Find out more about WAF](/edge-services/reference-content/understanding-waf/).
5757

5858
The summary cost for the creation of this pipeline is displayed, notably whether it falls within the limits of your current [subscription plan](/edge-services/reference-content/understanding-pricing/)
5959

pages/edge-services/quickstart.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ You can create [pipelines](/edge-services/concepts/#pipeline) for either Object
8282

8383
7. Optionally, configure **Advanced Settings:**
8484
- **Cache**: When enabled, content from your Load Balancer origin is cached with Edge Services and served directly to users from Edge Services' servers. Set a **Lifetime** value, in seconds, to dictate how long objects should remain in the cache before being freshly retrieved from the origin. [Find out more about caching](/edge-services/how-to/configure-cache/).
85-
- **WAF**: When enabled, requests to your Load Balancer origin are evaluated by a **W**eb **A**application **F**irewall. Malicious requests are blocked or logged, depending on your settings. Set a paranoia level to determine WAF's aggressivity, and a mode (block or log) for dealing with malicious requests. [Find out more about WAF](/edge-services/reference-content/understanding-waf/).
85+
- **WAF**: When enabled, requests to your Load Balancer origin are evaluated by a **W**eb **A**pplication **F**irewall. Malicious requests are blocked or logged, depending on your settings. Set a paranoia level to determine WAF's aggressivity, and a mode (block or log) for dealing with malicious requests. [Find out more about WAF](/edge-services/reference-content/understanding-waf/).
8686

8787
8. Check the summary cost for the pipeline, and click **Create Edge Services pipeline**.
8888

@@ -178,7 +178,7 @@ Your customized domain is set up, and you are returned to the Edge Services dash
178178

179179
## How to configure caching and WAF
180180

181-
Enabling a cache and/or a **W**eb **A**application **F**irewall on your Edge Services pipeline are both optional steps.
181+
Enabling a cache and/or a **W**eb **A**pplication **F**irewall on your Edge Services pipeline are both optional steps.
182182

183183
- Enabling a **cache** means that Edge Services stores copies of files from your origin, and can serve them directly to users from this cache rather then fetching them freshly from your bucket or Load Balancer origin each time. This reduces load on your origin and can improve performance. [Find out how to configure a cache](/edge-services/how-to/configure-cache/)
184184

pages/edge-services/reference-content/understanding-waf.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ import image from './assets/scaleway-edge-services-waf-diag.webp'
1010
import image2 from './assets/scaleway-edge-services-pipeline-diag.webp'
1111

1212

13-
You can choose to enable the **W**eb **A**application **F**irewall (WAF) feature on your Edge Services pipeline, for added protection. This documentation page gives a detailed overview of WAF, and the different settings, modes and functionalities available.
13+
You can choose to enable the **W**eb **A**pplication **F**irewall (WAF) feature on your Edge Services pipeline, for added protection. This documentation page gives a detailed overview of WAF, and the different settings, modes and functionalities available.
1414

1515
## WAF overview
1616

0 commit comments

Comments
 (0)