diff --git a/changelog/august2025/2025-08-14-generative-apis-added-gpt-oss-and-qwen3-coder-are-now-a.mdx b/changelog/august2025/2025-08-14-generative-apis-added-gpt-oss-and-qwen3-coder-are-now-a.mdx index e9ea4d9093..bc9699daa6 100644 --- a/changelog/august2025/2025-08-14-generative-apis-added-gpt-oss-and-qwen3-coder-are-now-a.mdx +++ b/changelog/august2025/2025-08-14-generative-apis-added-gpt-oss-and-qwen3-coder-are-now-a.mdx @@ -8,5 +8,5 @@ product: generative-apis [GPT-OSS](/generative-apis/reference-content/supported-models/), [Qwen3 Coder](/generative-apis/reference-content/supported-models/) and [Mistral Small 3.2](/generative-apis/reference-content/supported-models/) are now available on Generative APIs. -GPT-OSS is a frontier open source model with significant reasoning capabilities and increased tokens thoughput performance. +GPT-OSS is a frontier open source model with significant reasoning capabilities and increased tokens throughput performance. diff --git "a/changelog/databases/january2023/2023-01-06-redistm-added-managed-database-for-redis\342\204\242.mdx" "b/changelog/databases/january2023/2023-01-06-redistm-added-managed-database-for-redis\342\204\242.mdx" index ce82e16cef..d58eb45bb3 100644 --- "a/changelog/databases/january2023/2023-01-06-redistm-added-managed-database-for-redis\342\204\242.mdx" +++ "b/changelog/databases/january2023/2023-01-06-redistm-added-managed-database-for-redis\342\204\242.mdx" @@ -1,5 +1,5 @@ --- -title: Managed Database for Redis™ has a new Availabilty Zone! +title: Managed Database for Redis™ has a new Availability Zone! status: added author: fullname: 'Join the #managed-database-for-redis channel on Slack.' diff --git a/changelog/june2024/2024-06-18-load-balancers-changed-static-private-network-attachmen.mdx b/changelog/june2024/2024-06-18-load-balancers-changed-static-private-network-attachmen.mdx index 8cee1c76f2..7404f76170 100644 --- a/changelog/june2024/2024-06-18-load-balancers-changed-static-private-network-attachmen.mdx +++ b/changelog/june2024/2024-06-18-load-balancers-changed-static-private-network-attachmen.mdx @@ -9,9 +9,9 @@ category: network product: load-balancers --- -Following the deprecation of [static Private Network attachment](https://www.scaleway.com/en/docs/changelog/?product=load-balancers&status=deprecated#static-attachment-is-no-longer-available), the Load Balancer API will no longer accept static Private Network attachement with an IP address outside of the Private Network subnet. +Following the deprecation of [static Private Network attachment](https://www.scaleway.com/en/docs/changelog/?product=load-balancers&status=deprecated#static-attachment-is-no-longer-available), the Load Balancer API will no longer accept static Private Network attachment with an IP address outside of the Private Network subnet. Please update to [DHCP attachment type](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-private-networks-attach-a-load-balancer-to-a-private-network) (recommended) or use an IP address which belongs to the Private Network subnet. -If you already use DHCP attachment mode or static attachement mode with an IP address belonging to the Private Network subnet, you're not affected by this change. +If you already use DHCP attachment mode or static attachment mode with an IP address belonging to the Private Network subnet, you're not affected by this change. diff --git a/changelog/march2024/2024-03-28-jobs-added-serverless-jobs-is-now-in-ga.mdx b/changelog/march2024/2024-03-28-jobs-added-serverless-jobs-is-now-in-ga.mdx index 92d61519ac..e0b0af7e1f 100644 --- a/changelog/march2024/2024-03-28-jobs-added-serverless-jobs-is-now-in-ga.mdx +++ b/changelog/march2024/2024-03-28-jobs-added-serverless-jobs-is-now-in-ga.mdx @@ -9,5 +9,5 @@ category: serverless product: jobs --- -Serverless Jobs is now in GA. Severless Jobs allows you to to run simple tasks per batch in the cloud without having to worry about infrastructure management. Find out more about it in [our dedicated documentation](/serverless-jobs/). +Serverless Jobs is now in GA. Serverless Jobs allows you to to run simple tasks per batch in the cloud without having to worry about infrastructure management. Find out more about it in [our dedicated documentation](/serverless-jobs/). diff --git a/changelog/march2025/2025-03-25-functions-changed-functions-runtimes-update.mdx b/changelog/march2025/2025-03-25-functions-changed-functions-runtimes-update.mdx index a106c95e9d..bdf163794f 100644 --- a/changelog/march2025/2025-03-25-functions-changed-functions-runtimes-update.mdx +++ b/changelog/march2025/2025-03-25-functions-changed-functions-runtimes-update.mdx @@ -30,4 +30,4 @@ product: functions * Python 3.7 -For additional informations about Serverless Functions runtimes, check the [dedicated documentation](/serverless-functions/reference-content/functions-runtimes/). +For additional information about Serverless Functions runtimes, check the [dedicated documentation](/serverless-functions/reference-content/functions-runtimes/). diff --git a/changelog/serverless/january2023/2023-01-11-fixed-functions-doublecorserror.mdx b/changelog/serverless/january2023/2023-01-11-fixed-functions-doublecorserror.mdx index 6f13439c49..84e0b95ede 100644 --- a/changelog/serverless/january2023/2023-01-11-fixed-functions-doublecorserror.mdx +++ b/changelog/serverless/january2023/2023-01-11-fixed-functions-doublecorserror.mdx @@ -9,4 +9,4 @@ category: serverless product: functions --- -The double CORS error that occasionally occurred on Serveless Functions has been fixed. \ No newline at end of file +The double CORS error that occasionally occurred on Serverless Functions has been fixed. \ No newline at end of file diff --git a/macros/iot-hub/iot.mdx b/macros/iot-hub/iot.mdx index 7d1486b355..74b4d5cc7a 100644 --- a/macros/iot-hub/iot.mdx +++ b/macros/iot-hub/iot.mdx @@ -2,4 +2,4 @@ macro: iot-hub-iot --- -**IoT Hub** is a managed **message broker** that dispaches messages between **devices**, **services** and **applications** using a publish/subscribe pattern. \ No newline at end of file +**IoT Hub** is a managed **message broker** that dispatches messages between **devices**, **services** and **applications** using a publish/subscribe pattern. \ No newline at end of file diff --git a/pages/account/reference-content/scaleway-network-information.mdx b/pages/account/reference-content/scaleway-network-information.mdx index f8b428583e..e077fb6fae 100644 --- a/pages/account/reference-content/scaleway-network-information.mdx +++ b/pages/account/reference-content/scaleway-network-information.mdx @@ -113,7 +113,7 @@ DNS cache servers and NTP servers are available in every Availability Zone. Thei Generic: `rdate.dedibox.com` - Primary rdate server: `51.159.47.151` (`ntp1.online.net`) -- Seconday rdate server: `51.158.192.3` (`ntp2.online.net`) +- Secondary rdate server: `51.158.192.3` (`ntp2.online.net`) Backup server: `dedibackup.dedibox.fr` diff --git a/pages/apple-silicon/how-to/setup-vm-with-utm.mdx b/pages/apple-silicon/how-to/setup-vm-with-utm.mdx index 16b4f62648..699277ebb9 100644 --- a/pages/apple-silicon/how-to/setup-vm-with-utm.mdx +++ b/pages/apple-silicon/how-to/setup-vm-with-utm.mdx @@ -25,7 +25,7 @@ UTM is a free and open-source software that leverages Apple's Hypervisor framewo - A [Mac mini](/apple-silicon/how-to/create-mac-mini/) - [VNC access](/apple-silicon/how-to/access-remote-desktop-mac-mini/) to your Mac -## Installating UTM +## Installing UTM 1. Download and install UTM on the Mac mini: * From the official [Mac App Store](https://apps.apple.com/us/app/utm-virtual-machines/id1538878817) or diff --git a/pages/audit-trail/concepts.mdx b/pages/audit-trail/concepts.mdx index 69ac3a5952..6b945ab810 100644 --- a/pages/audit-trail/concepts.mdx +++ b/pages/audit-trail/concepts.mdx @@ -8,7 +8,7 @@ dates: ## Audit Trail -Audit Trail is a tool that holds a record of events and changes performed within a Scaleway Organization. Audit Trail allows you to keep track of all actions, whether successful, attempted, or failed, perfomed on your Scaleway resources. +Audit Trail is a tool that holds a record of events and changes performed within a Scaleway Organization. Audit Trail allows you to keep track of all actions, whether successful, attempted, or failed, performed on your Scaleway resources. With Audit Trail you can view actions taken by any [principal](/iam/concepts/#principal) in any Project and on any of your Scaleway resources. You can also see the API methods used, the outcome of the action performed (status), and the IP address from which a principal performed an action. diff --git a/pages/audit-trail/troubleshooting/cannot-see-events.mdx b/pages/audit-trail/troubleshooting/cannot-see-events.mdx index 7417cb842a..8b9d894067 100644 --- a/pages/audit-trail/troubleshooting/cannot-see-events.mdx +++ b/pages/audit-trail/troubleshooting/cannot-see-events.mdx @@ -16,7 +16,7 @@ I cannot see any events in Audit Trail. ## Possible solutions -- Make sure that you have the [permision set necessary to access Audit Trail](/audit-trail/how-to/configure-audit-trail-permissions). If you are not an IAM manager, contact your IAM manager to ask for Audit Trail access. +- Make sure that you have the [permission set necessary to access Audit Trail](/audit-trail/how-to/configure-audit-trail-permissions). If you are not an IAM manager, contact your IAM manager to ask for Audit Trail access. - Make sure you have created Scaleway resources to see events in Audit Trail. diff --git a/pages/cockpit/how-to/send-metrics-from-k8s-to-cockpit.mdx b/pages/cockpit/how-to/send-metrics-from-k8s-to-cockpit.mdx index df93ac588c..03a94d2d92 100644 --- a/pages/cockpit/how-to/send-metrics-from-k8s-to-cockpit.mdx +++ b/pages/cockpit/how-to/send-metrics-from-k8s-to-cockpit.mdx @@ -70,7 +70,7 @@ alloy-singleton: ## Add annotations for auto-discovery -Annotations in Kubernetes provide a way to attach metadata to your resources. For `k8s-monitoring`, these annotations signal which Pods should be scraped for metrics, and what port to use. These annotations have to be on the Pods that the deployement will spawn so they have to be in the Pod template, not the deployement itself. +Annotations in Kubernetes provide a way to attach metadata to your resources. For `k8s-monitoring`, these annotations signal which Pods should be scraped for metrics, and what port to use. These annotations have to be on the Pods that the deployment will spawn so they have to be in the Pod template, not the deployment itself. In this documentation we are adding annotations to specify we want `k8s-monitoring` to scrape the Pods from our deployment. Make sure that you replace `$METRICS_PORT` with the port where your application exposes Prometheus metrics. ### Kubernetes deployment template diff --git a/pages/container-registry/faq.mdx b/pages/container-registry/faq.mdx index 67f4aed08c..81111d7f95 100644 --- a/pages/container-registry/faq.mdx +++ b/pages/container-registry/faq.mdx @@ -20,7 +20,7 @@ The Service is currently available in our `nl-ams` (Amsterdam, The Netherlands), Scaleway Container Registry is billed based on stored images size, and outgoing data transfer. -| | Stored Images | Outgoing data transfer | Incoming data transfert | +| | Stored Images | Outgoing data transfer | Incoming data transfer | |----------------|-----------------|--------------------------------------------------|-------------------------| | Private images | €0.027/GB/month | Inter-regional: €0.033/GB - Intra-regional: free | Free | | Public images | Free up to 75GB | Inter-regional: free - Intra-regional: free | Free | diff --git a/pages/dedibox-account/how-to/disable-two-factor-authentication.mdx b/pages/dedibox-account/how-to/disable-two-factor-authentication.mdx index 86a29eb6d9..f2fe0c6a6e 100644 --- a/pages/dedibox-account/how-to/disable-two-factor-authentication.mdx +++ b/pages/dedibox-account/how-to/disable-two-factor-authentication.mdx @@ -19,7 +19,7 @@ For security reasons, it is **not recommended to disable** multifactor authentic 1. Click your username, next to _logged in as_, in the top right corner of the Dedibox console. Then click **Security** in the pop-up menu. -2. The security page displays. Click **Disable two factor authenticaton**. +2. The security page displays. Click **Disable two factor authentication**. 3. Enter a security token generated by your multifactor authentication application and click **Confirm**. Multifactor authentication is now disabled, and you can log in with your identifier and password only. diff --git a/pages/dedibox-hardware/index.mdx b/pages/dedibox-hardware/index.mdx index 9463f4e28a..7daa0f26d9 100644 --- a/pages/dedibox-hardware/index.mdx +++ b/pages/dedibox-hardware/index.mdx @@ -6,7 +6,7 @@ description: Dive into Scaleway Dedibox - Hardware with our quickstart guides, h diff --git a/pages/dedibox-ip-failover/menu.ts b/pages/dedibox-ip-failover/menu.ts index 5e7efc31a0..1a508404f0 100644 --- a/pages/dedibox-ip-failover/menu.ts +++ b/pages/dedibox-ip-failover/menu.ts @@ -43,7 +43,7 @@ export const dediboxIpFailoverMenu = { slug: 'configure-windows', }, { - label: 'Create a vitual MAC address', + label: 'Create a virtual MAC address', slug: 'create-virtual-mac', }, { diff --git a/pages/dedibox-ipv6/quickstart.mdx b/pages/dedibox-ipv6/quickstart.mdx index 623640cdf6..cc628079fb 100644 --- a/pages/dedibox-ipv6/quickstart.mdx +++ b/pages/dedibox-ipv6/quickstart.mdx @@ -37,7 +37,7 @@ All Scaleway Dedibox dedicated servers support IPv6. You can request a free /48 Activation of IPv6 SLAAC assigns **one** `/128` IPv6 subnet to your server (one usable IPv6 address). This IP will be statically linked to your server and can not be attributed to another server. - + This feature is not yet available for all servers. Only the servers that are compatible will show the related button. diff --git a/pages/dedibox-kvm-over-ip/quickstart.mdx b/pages/dedibox-kvm-over-ip/quickstart.mdx index 68eae55b4d..2ecc06fdb5 100644 --- a/pages/dedibox-kvm-over-ip/quickstart.mdx +++ b/pages/dedibox-kvm-over-ip/quickstart.mdx @@ -37,7 +37,7 @@ In this document, we show you how to access the IPMI for a Dell or HP server. Se ## How to use IPMI via Dell iDRAC -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. +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. 1. From the console, click **Server** > **Server list**. A list of your servers displays. 2. Click **Manage** next to the relevant server. @@ -58,7 +58,7 @@ IPMI is a standard specification for a remote management subsystem. On a Dell se ## How to use IPMI via HPE iLO -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. +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. 1. From the console, click **Server** > **Server list**. A list of your servers displays. 2. Click **Manage** next to the relevant server. diff --git a/pages/dedibox/how-to/use-ipmi-on-server.mdx b/pages/dedibox/how-to/use-ipmi-on-server.mdx index fc4b62ecaf..4a9c58ee46 100644 --- a/pages/dedibox/how-to/use-ipmi-on-server.mdx +++ b/pages/dedibox/how-to/use-ipmi-on-server.mdx @@ -38,7 +38,7 @@ In this document, we show you how to access the IPMI for a Dell or HP server. Se ## How to use IPMI via Dell iDRAC -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. +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. 1. From the console, click **Server** > **Server list**. A list of your servers displays. 2. Click **Manage** next to the relevant server. @@ -59,7 +59,7 @@ IPMI is a standard specification for a remote management subsystem. On a Dell se ## How to use IPMI via HP iLO -IPMI is a standard specification for a remote management subsystem. On a Dell server, IPMI is realized through the ILO: the **i**ntegrated **L**ights **O**ut processor. +IPMI is a standard specification for a remote management subsystem. On a Dell server, IPMI is realized through the ILO: the **I**ntegrated **L**ights **O**ut processor. 1. From the console, click **Server** > **Server list**. A list of your servers displays. 2. Click **Manage** next to the relevant server. diff --git a/pages/elastic-metal/how-to/configure-flexible-ipv6.mdx b/pages/elastic-metal/how-to/configure-flexible-ipv6.mdx index 8d1ca0a206..66e7e5405d 100644 --- a/pages/elastic-metal/how-to/configure-flexible-ipv6.mdx +++ b/pages/elastic-metal/how-to/configure-flexible-ipv6.mdx @@ -67,7 +67,7 @@ Ubuntu uses [netplan](https://netplan.io) for network configuration since Ubuntu version: 2 ``` - Replace `eno1` with the correct name of your internet interface. - - Replace the [IP addresses of the resolving DNS servers (nameservers)](/account/reference-content/scaleway-network-information/#dns-cache-servers) with the ones located in the same geographical location as your machine for best perfomances. + - Replace the [IP addresses of the resolving DNS servers (nameservers)](/account/reference-content/scaleway-network-information/#dns-cache-servers) with the ones located in the same geographical location as your machine for best performances. The configuration example above is valid for the main IP address of your Dedibox server. For IPv6 on a [virtual machine](/dedibox-network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines), use the unique gateway for the failover IPv4. diff --git a/pages/elastic-metal/troubleshooting/troubleshoot-ssh-issues.mdx b/pages/elastic-metal/troubleshooting/troubleshoot-ssh-issues.mdx index c3900313a8..4dfe4d498b 100644 --- a/pages/elastic-metal/troubleshooting/troubleshoot-ssh-issues.mdx +++ b/pages/elastic-metal/troubleshooting/troubleshoot-ssh-issues.mdx @@ -53,5 +53,5 @@ You are unable to connect to your Scaleway Elastic Metal server via SSH. #### Add the new SSH key to the existent system - Reboot in rescue mode as explained in this [documentation](/elastic-metal/how-to/use-rescue-mode/) -- Mount filesystem in rescue mode to access data and files by folowing these [steps](/elastic-metal/troubleshooting/troubleshoot-rescue-your-data/##mounting-partitions) +- Mount filesystem in rescue mode to access data and files by following these [steps](/elastic-metal/troubleshooting/troubleshoot-rescue-your-data/##mounting-partitions) - Modify the "authorized_keys" file to add your new SSH public key at the end diff --git a/pages/generative-apis/reference-content/data-privacy.mdx b/pages/generative-apis/reference-content/data-privacy.mdx index a4d7320467..ce8281393e 100644 --- a/pages/generative-apis/reference-content/data-privacy.mdx +++ b/pages/generative-apis/reference-content/data-privacy.mdx @@ -26,7 +26,7 @@ We collect and process the following categories of data: - Token counts (input/output specific to large language models (LLMs), without prompt details) - Parameters defined by the user, **excluding the actual content of the prompts (system, user, etc.)** -Only in the event of misuse harming the service functionnality (such as specific customer requests generating errors or carrying out malicious activity), we may store temporarily and access full content of HTTP requests of this customer, to identify a root cause issue or any security vulnerability. +Only in the event of misuse harming the service functionality (such as specific customer requests generating errors or carrying out malicious activity), we may store temporarily and access full content of HTTP requests of this customer, to identify a root cause issue or any security vulnerability. ## 3. How we use your data diff --git a/pages/generative-apis/reference-content/model-lifecycle.mdx b/pages/generative-apis/reference-content/model-lifecycle.mdx index b1c041410e..b831e74320 100644 --- a/pages/generative-apis/reference-content/model-lifecycle.mdx +++ b/pages/generative-apis/reference-content/model-lifecycle.mdx @@ -1,7 +1,7 @@ --- title: Understand Generative APIs model lifecycle description: Learn about the lifecycle of generative AI models in Scaleway. This page explains how each status affects model usage and updates, ensuring you are informed about transitions and how to access the latest model versions. -tags: generative-apis ai-data model-lifecyle +tags: generative-apis ai-data model-lifecycle dates: validation: 2025-09-22 posted: 2024-09-02 diff --git a/pages/generative-apis/reference-content/supported-models.mdx b/pages/generative-apis/reference-content/supported-models.mdx index 84c5df4869..93d26aace8 100644 --- a/pages/generative-apis/reference-content/supported-models.mdx +++ b/pages/generative-apis/reference-content/supported-models.mdx @@ -71,7 +71,7 @@ Our [Embeddings API](/generative-apis/how-to/query-embedding-models) provides bu ## Deprecated models -These models can still be accessed in Generative APIs, but their End of Life (EOL) is planned according to our [model lifecyle policy](/generative-apis/reference-content/model-lifecycle/). +These models can still be accessed in Generative APIs, but their End of Life (EOL) is planned according to our [model lifecycle policy](/generative-apis/reference-content/model-lifecycle/). Deprecated models should not be queried anymore. We recommend to use newer models available in Generative APIs or to deploy these models in dedicated [Managed Inference](https://console.scaleway.com/inference/deployments) deployments. | Provider | Model string | End of Life (EOL) date diff --git a/pages/gpu/how-to/use-gpu-with-docker.mdx b/pages/gpu/how-to/use-gpu-with-docker.mdx index cbcbd50f5a..2c0177ad0a 100644 --- a/pages/gpu/how-to/use-gpu-with-docker.mdx +++ b/pages/gpu/how-to/use-gpu-with-docker.mdx @@ -92,7 +92,7 @@ Below is a list of the most common commands you use when dealing with Docker con | **docker stop** | `docker stop ` | This command is used to stop a running container with the ID ``. This command allows the container to shut down gracefully. | | **docker kill** | `docker kill ` | This command is used to "kill" a running container with the ID ``. This command ends the execution of the container immediately. | | **docker build** | `docker build ` | This command is used to build a new image from a specified Dockerfile. | -| **docker commit** | `docker commit ` | This command is used to create a new local image of an edited container. | +| **docker commit** | `docker commit ` | This command is used to create a new local image of an edited container. | | **docker tag** | `docker tag ` or `docker tag /` | This command is used to tag a local image (necessary before pushing to a registry). An image can have multiple tags, like a specific version or "latest". | | **docker push** | `docker push ` | This command is used to push a local image to a remote repository. | | **docker images** | `docker images` | This command is used to list all available Docker images on the local system. | diff --git a/pages/gpu/reference-content/choosing-gpu-instance-type.mdx b/pages/gpu/reference-content/choosing-gpu-instance-type.mdx index 3d3fe00db5..5b6dfb72aa 100644 --- a/pages/gpu/reference-content/choosing-gpu-instance-type.mdx +++ b/pages/gpu/reference-content/choosing-gpu-instance-type.mdx @@ -88,7 +88,7 @@ Remember that there is no one-size-fits-all answer, and the right GPU Instance t | [Scratch Storage](/gpu/how-to/use-scratch-storage-h100-instances/) | No | No | No | No | | [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | No | No | No | No | | Bandwidth | 2.5 Gbps | 5 Gbps | 10 Gbps | 20 Gbps | -| Better used for | Image Enconding (8K) | Video Enconding (8K) | 7B LLM Inference | 70B LLM Inference | +| Better used for | Image Encoding (8K) | Video Encoding (8K) | 7B LLM Inference | 70B LLM Inference | | What they are not made for | Training of LLM | Training of LLM | Training of LLM | Training of LLM | | | **[L40S-1-48G](https://www.scaleway.com/en/contact-l40s/)** | **[L40S-2-48G](https://www.scaleway.com/en/contact-l40s/)** | **[L40S-4-48G](https://www.scaleway.com/en/contact-l40s/)** | **[L40S-8-48G](https://www.scaleway.com/en/contact-l40s/)** | diff --git a/pages/gpu/reference-content/understanding-nvidia-fp8.mdx b/pages/gpu/reference-content/understanding-nvidia-fp8.mdx index 814307d067..00362b6b6a 100644 --- a/pages/gpu/reference-content/understanding-nvidia-fp8.mdx +++ b/pages/gpu/reference-content/understanding-nvidia-fp8.mdx @@ -21,4 +21,4 @@ The `E5M2` format adapts the IEEE FP16 format, allocating five bits to the expon The FP8 standard preserves accuracy comparable to 16-bit formats across a wide range of applications, architectures, and networks. -For more information about the FP8 standard, and instructions how to use it with H100 GPU Instances, refer to NVIDIA's [offical FP8 documentation](https://docs.nvidia.com/deeplearning/transformer-engine/user-guide/examples/fp8_primer.html) and the [code example repository](https://github.com/NVIDIA/TransformerEngine/tree/main/examples). \ No newline at end of file +For more information about the FP8 standard, and instructions how to use it with H100 GPU Instances, refer to NVIDIA's [official FP8 documentation](https://docs.nvidia.com/deeplearning/transformer-engine/user-guide/examples/fp8_primer.html) and the [code example repository](https://github.com/NVIDIA/TransformerEngine/tree/main/examples). \ No newline at end of file diff --git a/pages/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx b/pages/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx index c953fb47fd..ec915a4bcd 100644 --- a/pages/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx +++ b/pages/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx @@ -1,7 +1,7 @@ --- title: Installing NVIDIA drivers on Ubuntu 22.04 description: This section provides information on how to install NVIDIA drivers on Ubuntu 22.04 -tags: gpu driver nvidia-driver unbuntu l4 l40s +tags: gpu driver nvidia-driver ubuntu l4 l40s dates: validation: 2025-10-14 posted: 2024-03-27 diff --git a/pages/guidelines.mdx b/pages/guidelines.mdx index b3cf60b843..8dec73c5fa 100644 --- a/pages/guidelines.mdx +++ b/pages/guidelines.mdx @@ -446,7 +446,7 @@ import myImage from "./assets/myImage.webp" ```` -All images must be in `webp` format, and stored in the page's `assets` folder. Image names must always start with `scaleway`, and the words should be hyphen-seperated. +All images must be in `webp` format, and stored in the page's `assets` folder. Image names must always start with `scaleway`, and the words should be hyphen-separated. ### When to include images diff --git a/pages/instances/how-to/create-a-backup.mdx b/pages/instances/how-to/create-a-backup.mdx index 04e8381eb6..1b6c21feaa 100644 --- a/pages/instances/how-to/create-a-backup.mdx +++ b/pages/instances/how-to/create-a-backup.mdx @@ -28,7 +28,7 @@ This feature is available on Instance types. Creating images of your Instance is 1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Click the Instance you want to back up. -3. Go to the **Images** section of the Instace's overview page. +3. Go to the **Images** section of the Instance's overview page. 4. Click **Create image from Instance**. A pop-up displays asking you to confirm the action. 5. Click **Create image from Instance**. You are returned to the **Storage** tab, where your new image now displays. diff --git a/pages/instances/how-to/create-image-from-snapshot.mdx b/pages/instances/how-to/create-image-from-snapshot.mdx index 9818fd3419..2668d84c3a 100644 --- a/pages/instances/how-to/create-image-from-snapshot.mdx +++ b/pages/instances/how-to/create-image-from-snapshot.mdx @@ -46,7 +46,7 @@ scw instance image create snapshot-id="$SCW_VOLUME_ID_1" additional-volumes.0.id - Ensure the architecture (`arch`) is set to a valid value (e.g., `x86_64`). - Supported arguments for the image create commmand include: + Supported arguments for the image create command include: ``` ARGS: [name=] Name of the image diff --git a/pages/instances/how-to/migrate-local-storage-to-sbs.mdx b/pages/instances/how-to/migrate-local-storage-to-sbs.mdx index b425a89302..e66815dc84 100644 --- a/pages/instances/how-to/migrate-local-storage-to-sbs.mdx +++ b/pages/instances/how-to/migrate-local-storage-to-sbs.mdx @@ -83,7 +83,7 @@ After attaching the new SBS volume, you need to restart your instance. This will By following these steps, you have successfully migrated your local storage (`l_ssd`) to Scaleway Block Storage (SBS). Your Instance is now up and running using SBS, and you can benefit from the advantages of Scaleway's advanced Block Storage solution. -For furher information, refer to [How to migrate existing volumes and snapshots to Scaleway's new Block Storage management](/instances/how-to/migrate-volumes-snapshots-to-sbs/). +For further information, refer to [How to migrate existing volumes and snapshots to Scaleway's new Block Storage management](/instances/how-to/migrate-volumes-snapshots-to-sbs/). This tutorial does not cover specific modifications done by the user in the Instance that would break the mounting system. diff --git a/pages/instances/menu.ts b/pages/instances/menu.ts index e77752f1f2..f66d64cce3 100644 --- a/pages/instances/menu.ts +++ b/pages/instances/menu.ts @@ -159,7 +159,7 @@ export const instancesMenu = { "slug": "choosing-instance-type" }, { - "label": "Choosing bewteen shared or dedicated CPUs", + "label": "Choosing between shared or dedicated CPUs", "slug": "choosing-shared-vs-dedicated-cpus" }, { @@ -228,7 +228,7 @@ export const instancesMenu = { }, { "label": "Compatibility between Scaleway OS Images and Flexible IPs", - "slug": "comaptibility-scw-os-images-flexible-ip" + "slug": "compatibility-scw-os-images-flexible-ip" }, { "label": "Enabling DHCP network configuration for Windows Server 2022 Instances", diff --git a/pages/instances/reference-content/comaptibility-scw-os-images-flexible-ip.mdx b/pages/instances/reference-content/compatibility-scw-os-images-flexible-ip.mdx similarity index 100% rename from pages/instances/reference-content/comaptibility-scw-os-images-flexible-ip.mdx rename to pages/instances/reference-content/compatibility-scw-os-images-flexible-ip.mdx diff --git a/pages/instances/reference-content/identify-devices.mdx b/pages/instances/reference-content/identify-devices.mdx index f772190b51..028061342a 100644 --- a/pages/instances/reference-content/identify-devices.mdx +++ b/pages/instances/reference-content/identify-devices.mdx @@ -1,5 +1,5 @@ --- -title: Identifiying devices of a Scaleway Instance +title: Identifying devices of a Scaleway Instance description: This page explains how to identify devices on a Scaleway Instance tags: instance dates: diff --git a/pages/instances/reference-content/manual-configuration-private-ips.mdx b/pages/instances/reference-content/manual-configuration-private-ips.mdx index ba0ff64914..99c03f432b 100644 --- a/pages/instances/reference-content/manual-configuration-private-ips.mdx +++ b/pages/instances/reference-content/manual-configuration-private-ips.mdx @@ -75,7 +75,7 @@ Once you have [added your Instances to a Private Network](/instances/how-to/use- - The network interface name is not guaranteed to be stable and may change across reboot or poweroff and poweron actions, similarily to the rest of the PCI hierarchy. + The network interface name is not guaranteed to be stable and may change across reboot or poweroff and poweron actions, similarly to the rest of the PCI hierarchy. 4. For convenience, you can give a more significant name (e.g. `priv0`) to the Private Network interface. Configure the new interface name as follows: ```bash @@ -139,7 +139,7 @@ Once you have brought up the Private Network via the previous steps, you can con NETMASK=255.255.255.0 IPADDR=192.168.43.4 ARP=yes - # replace HWADDR with the MAC address assoicated to the interface + # replace HWADDR with the MAC address associated to the interface HWADDR=02:00:00:00:1a:ae ``` diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index 4f060fee41..7ad09cff7e 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -30,7 +30,7 @@ The migration uses an intermediate Scaleway Instance as a converter, using tools Refer to [Scaleway’s Instance documentation](https://www.scaleway.com/en/docs/instances/) for details on setting up Instances and related services. - + If your virtual machine is running Windows, make sure to install the [virtiofs drivers](https://virtio-fs.gitlab.io/howto-windows.html) before exporting the VM. @@ -58,7 +58,7 @@ Review your VMware VMs to ensure compatibility with Scaleway Instances. 2. Check the disk configuration: - Record the number, size, and type of disks (e.g., 1x 100 GB VMDK). - For VMs with multiple disks, create individual snapshots and combine them into a single Scaleway image. Refer to the documentation on [how to create an image from a snapshot](/instances/how-to/create-image-from-snapshot/) for furher information. + For VMs with multiple disks, create individual snapshots and combine them into a single Scaleway image. Refer to the documentation on [how to create an image from a snapshot](/instances/how-to/create-image-from-snapshot/) for further information. 3. Verify the network configuration: - Note the number and type of network interfaces (NICs). @@ -153,7 +153,7 @@ This section outlines the migration of a Windows 2019 or 2022 VM with a single v bcdedit /emssettings EMSPORT:1 EMSBAUDRATE:115200 ``` - In the Adminstrator command prompt: + In the Administrator command prompt: ```cmd bcdedit /set {bootmgr} displaybootmenu yes diff --git a/pages/instances/troubleshooting/fix-common-issues.mdx b/pages/instances/troubleshooting/fix-common-issues.mdx index 32816480f4..25e70c0f30 100644 --- a/pages/instances/troubleshooting/fix-common-issues.mdx +++ b/pages/instances/troubleshooting/fix-common-issues.mdx @@ -218,7 +218,7 @@ This page lists the most common issues you may encounter with your Scaleway Inst - [Scaleway Troubleshooting: Fix unreachable Ubuntu Focal Instance when it has two public IP addresses](/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/) - [Scaleway Troubleshooting: Fix lost IPv6 connectivity on old Debian Buster images when migrating to routed IP](/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster/) - [Scaleway Troubleshooting: Fix unreachable IPv6 RHEL-based Instances after transitioning to routed IP](/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance/) -- [Netplan documenation](https://netplan.readthedocs.io/en/stable/) +- [Netplan documentation](https://netplan.readthedocs.io/en/stable/) ## Disk space errors with Instances diff --git a/pages/instances/troubleshooting/fix-error-message-in-scw-fetch-ssh-keys.mdx b/pages/instances/troubleshooting/fix-error-message-in-scw-fetch-ssh-keys.mdx index 7c98df9fe9..5d182468d4 100644 --- a/pages/instances/troubleshooting/fix-error-message-in-scw-fetch-ssh-keys.mdx +++ b/pages/instances/troubleshooting/fix-error-message-in-scw-fetch-ssh-keys.mdx @@ -27,7 +27,7 @@ The SSH keys will still be fetched, but this message may reappear in the file. ```. C:\ProgramData\ssh\administrators_authorized_keys if deleted. -To avoid this message, simply update the `ScalewayEcosystem` package using the folllowing +To avoid this message, simply update the `ScalewayEcosystem` package using the following commands: ``` Register-PSRepository -Name NuGet -SourceLocation https://api.nuget.org/v3/index.json -PublishLocation https://api.nuget.org/v3/index.json -InstallationPolicy Trusted diff --git a/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx b/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx index 9a814b0b0c..c04588a3fc 100644 --- a/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx +++ b/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx @@ -1,5 +1,5 @@ --- -title: Fix unreachable Ubuntu Focal Instance when it has two public IP adresses +title: Fix unreachable Ubuntu Focal Instance when it has two public IP addresses description: This page helps you recover or avoid unreachable Ubuntu 20.04 Focal Instance when it has two public IP addresses. tags: ubuntu-focal focal 20.04 multiple ipv4 ip dates: diff --git a/pages/instances/troubleshooting/index.mdx b/pages/instances/troubleshooting/index.mdx index 872d626c27..112266c1bb 100644 --- a/pages/instances/troubleshooting/index.mdx +++ b/pages/instances/troubleshooting/index.mdx @@ -70,7 +70,7 @@ productIcon: InstanceProductIcon - [Fix long delays when booting without a public IP](/instances/troubleshooting/fix-long-delays-booting-without-public-ip) - [Fix lost IPv6 connectivity on old Debian Buster images when migrating to routed IP](/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster) - [Fixing wrong PPA configuration on Ubuntu Noble Instances](/instances/troubleshooting/fix-noble-wrong-ppa-configuration) - - [Fix unreachable Ubuntu Focal Instance when it has two public IP adresses](/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips) + - [Fix unreachable Ubuntu Focal Instance when it has two public IP addresses](/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips) - [Fix unreachable IPv6 RHEL-based Instances after transitioning to routed IP](/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance) - [Fix unreachable Ubuntu Noble Instances following a reboot](/instances/troubleshooting/fix-unreachable-noble-after-reboot) - [Troubleshooting issues with faulty kernel installations](/instances/troubleshooting/reboot-from-faulty-kernel) diff --git a/pages/key-manager/api-cli/encrypt-decrypt-data-with-km-dek.mdx b/pages/key-manager/api-cli/encrypt-decrypt-data-with-km-dek.mdx index 24864d76c2..612cbd35a2 100644 --- a/pages/key-manager/api-cli/encrypt-decrypt-data-with-km-dek.mdx +++ b/pages/key-manager/api-cli/encrypt-decrypt-data-with-km-dek.mdx @@ -19,7 +19,7 @@ This page shows you how to encrypt and decrypt data using your Key Manager [data - Retrieved your key encryption key's ID - A valid [API key](/iam/how-to/create-api-keys/) - Downloaded and configured the [Scaleway CLI](https://github.com/scaleway/scaleway-cli?tab=readme-ov-file#getting-started) -- Dowloaded and installed [Go](https://go.dev/doc/install) +- Downloaded and installed [Go](https://go.dev/doc/install) - [Created a Key Manager data encryption key](/key-manager/how-to/create-manage-dek/) - [Created](/key-manager/how-to/create-km-key) and [retrieved the ID](/key-manager/how-to/retrieve-km-key-id) your Key Manager key diff --git a/pages/kubernetes/api-cli/cluster-monitoring.mdx b/pages/kubernetes/api-cli/cluster-monitoring.mdx index 33818996e9..fad806a8cd 100644 --- a/pages/kubernetes/api-cli/cluster-monitoring.mdx +++ b/pages/kubernetes/api-cli/cluster-monitoring.mdx @@ -137,7 +137,7 @@ Deploy `Grafana` to display the `Prometheus` metrics in some pre-defined dashboa 9. Choose `Prometheus` as data source and click **Import**. -10. Access the dashboard with metrics for Deployement, StatefulSet and DaemonSet: +10. Access the dashboard with metrics for Deployment, StatefulSet and DaemonSet: 11. You can also configure additional dashboards, for example, the node exporter full dashboard ([1860](https://grafana.com/grafana/dashboards/1860)) to display a dashboard with system metrics for each Kubernetes node: diff --git a/pages/kubernetes/how-to/connect-cluster-kubectl.mdx b/pages/kubernetes/how-to/connect-cluster-kubectl.mdx index a5eab9a06f..79056ebb4b 100644 --- a/pages/kubernetes/how-to/connect-cluster-kubectl.mdx +++ b/pages/kubernetes/how-to/connect-cluster-kubectl.mdx @@ -45,7 +45,7 @@ For detailed information about the configuration of IAM policies for your Kubern 5. Enter your existing Scaleway API key or click **Generate API key** to generate a new one. 6. (Optional) Enter API key specifics by selecting the API key bearer, and entering a description and expiration date for the key. Then click **Generate API key**. 7. The secret key of your API key displays. **Copy and store it** in a secure location. It will only be shown once. - 8. Click **Dowload kubeconfig** and run the command shown to export the path to the configuration file on your local machine. + 8. Click **Download kubeconfig** and run the command shown to export the path to the configuration file on your local machine. You can use the Scaleway CLI to automatically retrieve (and merge) your `kubeconfig` file, then interact with your Kubernetes cluster. diff --git a/pages/kubernetes/how-to/edit-cluster.mdx b/pages/kubernetes/how-to/edit-cluster.mdx index 114e71d0a5..9fba378dd1 100644 --- a/pages/kubernetes/how-to/edit-cluster.mdx +++ b/pages/kubernetes/how-to/edit-cluster.mdx @@ -1,7 +1,7 @@ --- title: How to manage a Kubernetes Kapsule cluster description: Learn how to manage your Scaleway Kubernetes Kapsule cluster, including adding nodes and pools via the Scaleway console. -tags: kubernetes kapsule-cluser +tags: kubernetes kapsule-cluster dates: validation: 2025-07-01 posted: 2021-05-31 diff --git a/pages/kubernetes/how-to/manage-node-pools.mdx b/pages/kubernetes/how-to/manage-node-pools.mdx index cda3a079cf..33030ade36 100644 --- a/pages/kubernetes/how-to/manage-node-pools.mdx +++ b/pages/kubernetes/how-to/manage-node-pools.mdx @@ -57,7 +57,7 @@ This documentation provides step-by-step instructions on how to manage Kubernete Alternatively, you can use the Scaleway CLI to [update a node pool](https://cli.scaleway.com/k8s/#update-a-pool-in-a-cluster). -## How to migrate existing workloads to a new Kubernets Kapsule node pool +## How to migrate existing workloads to a new Kubernetes Kapsule node pool Always ensure that your **data is backed up** before performing any operations that could affect it. diff --git a/pages/kubernetes/reference-content/kubernetes-load-balancer.mdx b/pages/kubernetes/reference-content/kubernetes-load-balancer.mdx index c31c8efc07..e639a4f746 100644 --- a/pages/kubernetes/reference-content/kubernetes-load-balancer.mdx +++ b/pages/kubernetes/reference-content/kubernetes-load-balancer.mdx @@ -88,7 +88,7 @@ You can refer to the [following example of webserver application to run.](https: 2. Use the command `kubectl create -f .yaml` to tell the Kubernetes Cloud Controller to create the Load Balancer from the manifest in the default namespace. -3. Run `kubectl get svc` to confirm that the Load Balancer Service has been created, and view its external IP. You can also check the [Load Balancer](https://console.scaleway.com/load-balancer/) section of the Scaleway console, where your Kuberenetes cluster's Load Balancer now appears. Note that you should **not** attempt to edit or delete the Load Balancer via the console, only via the manifest file and kubectl. +3. Run `kubectl get svc` to confirm that the Load Balancer Service has been created, and view its external IP. You can also check the [Load Balancer](https://console.scaleway.com/load-balancer/) section of the Scaleway console, where your Kubernetes cluster's Load Balancer now appears. Note that you should **not** attempt to edit or delete the Load Balancer via the console, only via the manifest file and kubectl. ## Specifying an IP address for your Load Balancer diff --git a/pages/kubernetes/reference-content/set-iam-permissions-and-implement-rbac.mdx b/pages/kubernetes/reference-content/set-iam-permissions-and-implement-rbac.mdx index acf168c083..6cf29dccaa 100644 --- a/pages/kubernetes/reference-content/set-iam-permissions-and-implement-rbac.mdx +++ b/pages/kubernetes/reference-content/set-iam-permissions-and-implement-rbac.mdx @@ -1,7 +1,7 @@ --- title: Setting IAM permissions and implementing RBAC on a cluster description: This page explains how to set IAM permissions and implement RBAC on a Scaleway Kubernetes cluster -tags: kubernetes kapsule-cluser +tags: kubernetes kapsule-cluster dates: validation: 2025-06-02 posted: 2025-06-02 diff --git a/pages/load-balancer/how-to/add-certificate.mdx b/pages/load-balancer/how-to/add-certificate.mdx index 336f916df7..d63ed8f8ab 100644 --- a/pages/load-balancer/how-to/add-certificate.mdx +++ b/pages/load-balancer/how-to/add-certificate.mdx @@ -117,7 +117,7 @@ Your certificate is added to your Load Balancer's frontend. Scaleway Load Balancers allow you to import **third party SSL certificates**. These are certificates issued by a Certificate Authority (CA) other than Let’s Encrypt. Depending on the CA, they may offer extended validation certificates which require full verification of the requesting entity’s legal identity before issuing the certificate. These certificates can be useful for websites that require a high trust level, like e-commerce or government websites, and can be easily imported into the Load Balancer configuration from the management console. -Alternatively you can also choose to import a **[self-signed certificate](#how-to-create-a-self-signed-certificate)**, not signed by any publically-trusted Certificate Authority, but perhaps suitable for development and testing purposes, or internal use. +Alternatively you can also choose to import a **[self-signed certificate](#how-to-create-a-self-signed-certificate)**, not signed by any publicly-trusted Certificate Authority, but perhaps suitable for development and testing purposes, or internal use. 1. Click **Load Balancers** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your Load Balancers displays. diff --git a/pages/load-balancer/reference-content/configuring-backends.mdx b/pages/load-balancer/reference-content/configuring-backends.mdx index 28a9406c8d..5fd963f88f 100644 --- a/pages/load-balancer/reference-content/configuring-backends.mdx +++ b/pages/load-balancer/reference-content/configuring-backends.mdx @@ -61,7 +61,7 @@ If none of the use cases above apply to the applications or metrics running on y Also, note that Proxy Protocol is more commonly activated for Load Balancers using TCP protocol. Load Balancers using HTTP protocol already pass information about the client IP address to the backend servers via an HTTP `X-Forwarded-For` [header](https://en.wikipedia.org/wiki/X-Forwarded-For), without needing to activate Proxy Protocol. If your Load Balancer uses HTTP protocol and you do not require the standardized information in the Proxy Protocol headers at the backend server, the `X-Forwarded-For` headers may be sufficient. -In order for Proxy Protocol to work, the backend server must support the selected Proxy Protocol. Different server softwares understand and process Proxy Protocol header information in different ways, and you may need to carry out specific configuration steps to ensure it is correctly received and processed. For example, for Nginx you might need to install and configure `ngx_http_realip_module`. Consult the documentation for your own server software, or see our [dedicated tutorial on configuring different web servers for Proxy Protocol v2](/tutorials/proxy-protocol-v2-load-balancer/) to help you get started. +In order for Proxy Protocol to work, the backend server must support the selected Proxy Protocol. Different server software understand and process Proxy Protocol header information in different ways, and you may need to carry out specific configuration steps to ensure it is correctly received and processed. For example, for Nginx you might need to install and configure `ngx_http_realip_module`. Consult the documentation for your own server software, or see our [dedicated tutorial on configuring different web servers for Proxy Protocol v2](/tutorials/proxy-protocol-v2-load-balancer/) to help you get started. #### Proxy Protocol versions diff --git a/pages/managed-databases-for-postgresql-and-mysql/api-cli/connecting-managed-databases-to-kubernetes-clusters.mdx b/pages/managed-databases-for-postgresql-and-mysql/api-cli/connecting-managed-databases-to-kubernetes-clusters.mdx index a2a7636f37..5dd9a47799 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/api-cli/connecting-managed-databases-to-kubernetes-clusters.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/api-cli/connecting-managed-databases-to-kubernetes-clusters.mdx @@ -68,7 +68,7 @@ Create a Private Network that both your Kubernetes cluster and database will use private-network.enable-ipam=true region-fr-par ``` -4. Get the Insance details and look for the public endpoint ID under the "Endpoints" section. +4. Get the Instance details and look for the public endpoint ID under the "Endpoints" section. ``` scw rdb instance get ``` diff --git a/pages/managed-databases-for-postgresql-and-mysql/faq.mdx b/pages/managed-databases-for-postgresql-and-mysql/faq.mdx index 8fe3329adc..336bea6650 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/faq.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/faq.mdx @@ -75,7 +75,7 @@ Then import the backup into your Scaleway Databases for `MySQL`: ## Which PostgreSQL extensions are available? -Refer to our dedicated [PostgreSQL extentions reference page](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) for a list of all available extensions and more details about each one. +Refer to our dedicated [PostgreSQL extensions reference page](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) for a list of all available extensions and more details about each one. ## Are my active and standby database nodes in a high-availability cluster hosted in the same data center? diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx index 644678be5e..2e63c69573 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx @@ -85,14 +85,14 @@ function header() { echo -e "\nRDB troubleshooting script\nThis script will run for several minutes to get enough information." header "Host information" if ! [ -x "$(command -v uname)" ]; then - echo 'Skipped: uname command is not availabe.' + echo 'Skipped: uname command is not available.' else uname -a fi header "Host connectivity check" if ! [ -x "$(command -v ping)" ]; then - echo 'Skipped: ping command is not availabe.' + echo 'Skipped: ping command is not available.' else ping -c 5 ${INSTANCE_IP} fi @@ -101,7 +101,7 @@ header "Database connectivity check" if ! [ -x "$(command -v telnet)" ]; then # try to fallback on curl telnet if ! [ -x "$(command -v curl)" ]; then - echo "Skipped: neither telnet nor curl command are availabe." + echo "Skipped: neither telnet nor curl command are available." else echo "(using curl)" timeout 2 curl -v telnet://$INSTANCE_IP:$INSTANCE_PORT @@ -113,7 +113,7 @@ fi header "Ip configuration check" if ! [ -x "$(command -v ip)" ]; then - echo 'Skipped: ip command is not availabe.' + echo 'Skipped: ip command is not available.' else echo -e "Interfaces:\n- \n" ip a diff --git a/pages/managed-databases-for-redis/api-cli/upgrade-redis-version.mdx b/pages/managed-databases-for-redis/api-cli/upgrade-redis-version.mdx index 496d09214f..dbff4c26a4 100644 --- a/pages/managed-databases-for-redis/api-cli/upgrade-redis-version.mdx +++ b/pages/managed-databases-for-redis/api-cli/upgrade-redis-version.mdx @@ -66,7 +66,7 @@ You can list your Database Instances to determine which ones need to be updated. 3. Run the following command. Make sure you replace `{cluster_id}` with the ID of your Database Instance. - Since we use a POST type call, you only need to edit the parameter that defines the version, the other confguration of your Database Instance will remain the same. + Since we use a POST type call, you only need to edit the parameter that defines the version, the other configuration of your Database Instance will remain the same. ```bash diff --git a/pages/managed-databases-for-redis/troubleshooting/database-instance-connectivity-issues.mdx b/pages/managed-databases-for-redis/troubleshooting/database-instance-connectivity-issues.mdx index 090f1fe4e2..5207e641d2 100644 --- a/pages/managed-databases-for-redis/troubleshooting/database-instance-connectivity-issues.mdx +++ b/pages/managed-databases-for-redis/troubleshooting/database-instance-connectivity-issues.mdx @@ -85,14 +85,14 @@ function header() { echo -e "\nREDIS troubleshooting script\nThis script will run for several minutes to get enough information." header "Host information" if ! [ -x "$(command -v uname)" ]; then - echo 'Skipped: uname command is not availabe.' + echo 'Skipped: uname command is not available.' else uname -a fi header "Host connectivity check" if ! [ -x "$(command -v ping)" ]; then - echo 'Skipped: ping command is not availabe.' + echo 'Skipped: ping command is not available.' else ping -c 5 ${INSTANCE_IP} fi @@ -101,7 +101,7 @@ header "Database connectivity check" if ! [ -x "$(command -v telnet)" ]; then # try to fallback on curl telnet if ! [ -x "$(command -v curl)" ]; then - echo "Skipped: neither telnet nor curl command are availabe." + echo "Skipped: neither telnet nor curl command are available." else echo "(using curl)" timeout 2 curl -v telnet://$INSTANCE_IP:$INSTANCE_PORT @@ -113,7 +113,7 @@ fi header "Ip configuration check" if ! [ -x "$(command -v ip)" ]; then - echo 'Skipped: ip command is not availabe.' + echo 'Skipped: ip command is not available.' else echo -e "Interfaces:\n- \n" ip a diff --git a/pages/managed-databases-for-redis/troubleshooting/index.mdx b/pages/managed-databases-for-redis/troubleshooting/index.mdx index 687c515638..2ef426a64b 100644 --- a/pages/managed-databases-for-redis/troubleshooting/index.mdx +++ b/pages/managed-databases-for-redis/troubleshooting/index.mdx @@ -36,8 +36,8 @@ productIcon: RedisProductIcon diff --git a/pages/managed-inference/reference-content/model-catalog.mdx b/pages/managed-inference/reference-content/model-catalog.mdx index 86a327d1f8..2688d542c3 100644 --- a/pages/managed-inference/reference-content/model-catalog.mdx +++ b/pages/managed-inference/reference-content/model-catalog.mdx @@ -140,7 +140,7 @@ mistral/mistral-small-3.1-24b-instruct-2503:fp8 - Bitmap (or raster) image formats, meaning storing images as grids of individual pixels, are supported. Vector image formats (SVG, PSD) are not supported, neither PDFs nor videos. - Images size are limited in the following ways: - Directly by the maximum context window. As an example, since tokens are squares of 28x28 pixels, the maximum context window taken by a single image is `3025` tokens (ie. `(1540*1540)/(28*28)`) - - Indirectly by the model accuracy: resolution above 1540x1540 will not increase model output accuracy. Indeed, images above 1540 pixels width or height will be automatically downscaled to fit within 1540x1540 dimension. Note that image ratio and overall aspect is preserved (images are not cropped, only additionaly compressed). + - Indirectly by the model accuracy: resolution above 1540x1540 will not increase model output accuracy. Indeed, images above 1540 pixels width or height will be automatically downscaled to fit within 1540x1540 dimension. Note that image ratio and overall aspect is preserved (images are not cropped, only additionally compressed). ### Pixtral-12b-2409 Pixtral is a vision language model introducing a novel architecture: 12B parameter multimodal decoder plus 400M parameter vision encoder. diff --git a/pages/managed-inference/reference-content/supported-models.mdx b/pages/managed-inference/reference-content/supported-models.mdx index 8f61a6acc1..463fcf5ca8 100644 --- a/pages/managed-inference/reference-content/supported-models.mdx +++ b/pages/managed-inference/reference-content/supported-models.mdx @@ -43,7 +43,7 @@ To deploy a custom model via Hugging Face, ensure the following: Your model repository must include: - * A `config.json` file containig: + * A `config.json` file containing: * An `architectures` array (see [supported architectures](#supported-models-architecture) for the exact list of supported values). * `max_position_embeddings` * Model weights in the [`.safetensors`](https://huggingface.co/docs/safetensors/index) format diff --git a/pages/managed-mongodb-databases/how-to/manage-users.mdx b/pages/managed-mongodb-databases/how-to/manage-users.mdx index 0cfa05e35b..d3fae56a19 100644 --- a/pages/managed-mongodb-databases/how-to/manage-users.mdx +++ b/pages/managed-mongodb-databases/how-to/manage-users.mdx @@ -50,7 +50,7 @@ Users can connect to a database and access its data. 8. Click **Confirm** after reviewing your configuration. -The list of your users is updated. You can see an overview of the global and speficic roles next to the name of each user. +The list of your users is updated. You can see an overview of the global and specific roles next to the name of each user. ## How to update user privileges diff --git a/pages/managed-mongodb-databases/quickstart.mdx b/pages/managed-mongodb-databases/quickstart.mdx index 7b7dac9766..028451790e 100644 --- a/pages/managed-mongodb-databases/quickstart.mdx +++ b/pages/managed-mongodb-databases/quickstart.mdx @@ -90,7 +90,7 @@ Follow the same procedure as above to connect to a private endpoint for one node ```bash mongosh "mongodb://{instance_id}-0.{privateNetworkName}" -u {username} ``` -### Connect to a private endpoint with mulitple nodes +### Connect to a private endpoint with multiple nodes For multiple nodes, replace `{db-instance-id}` with the Database Instance UUID of each respective Instance, and `{privateNetworkName}` with the names of your Private Network: diff --git a/pages/nats/how-to/create-credentials.mdx b/pages/nats/how-to/create-credentials.mdx index d64f720675..faa96c7b62 100644 --- a/pages/nats/how-to/create-credentials.mdx +++ b/pages/nats/how-to/create-credentials.mdx @@ -32,7 +32,7 @@ Credentials for NATS accounts are not granular: they necessarily give full read 3. Click the NATS account you want to generate credentials for. The account's **Overview** page displays. - + 4. In the **Credentials** panel, click **Generate credentials**. A pop-up displays. diff --git a/pages/nats/quickstart.mdx b/pages/nats/quickstart.mdx index 50345dbd72..a35dea94b3 100644 --- a/pages/nats/quickstart.mdx +++ b/pages/nats/quickstart.mdx @@ -53,7 +53,7 @@ Credentials for NATS accounts are not granular: they necessarily give full read 3. Click the NATS account you want to generate credentials for. The account's **Overview** page displays. - + 4. In the **Credentials** panel, click **Generate credentials**. A pop-up displays. diff --git a/pages/object-storage/api-cli/bucket-operations.mdx b/pages/object-storage/api-cli/bucket-operations.mdx index cf09c45882..3ba2d3f885 100644 --- a/pages/object-storage/api-cli/bucket-operations.mdx +++ b/pages/object-storage/api-cli/bucket-operations.mdx @@ -651,8 +651,8 @@ Content-Length: 124 **Sample response** ```sh no-copy HTTP/1.1 200 OK -x-amz-id-2: tx456e25b3558449a08b406-005caf132c -x-amz-request-id: tx456e25b3558449a08b406-005caf132c +x-amz-id-2: tx456e25b3558449a08b406-005calf132c +x-amz-request-id: tx456e25b3558449a08b406-005calf132c Date: Thu, 11 Apr 2019 10:13:00 GMT ``` **CLI command** diff --git a/pages/object-storage/how-to/get-started-edge-services.mdx b/pages/object-storage/how-to/get-started-edge-services.mdx index 2ca2ef4aba..1a866ec2b8 100644 --- a/pages/object-storage/how-to/get-started-edge-services.mdx +++ b/pages/object-storage/how-to/get-started-edge-services.mdx @@ -36,7 +36,7 @@ Find out more about pricing plans and how to subscribe to Edge Services in our [ Once you have subscribed to Edge Services, you are ready to create a pipeline. Follow the steps below. -You can create an Edge Services pipeline from the **Edge Services** section of the console, however, in this documentation, we describe how to create a pipeline directly from your bucket's dashboard in the **Objet Storage** section. +You can create an Edge Services pipeline from the **Edge Services** section of the console, however, in this documentation, we describe how to create a pipeline directly from your bucket's dashboard in the **Object Storage** section. 1. Click **Object Storage** in the **Storage** section of the [Scaleway console](https://console.scaleway.com/) side menu. diff --git a/pages/object-storage/how-to/upload-files-into-a-bucket.mdx b/pages/object-storage/how-to/upload-files-into-a-bucket.mdx index 3b3c0fa60b..25bef8c233 100644 --- a/pages/object-storage/how-to/upload-files-into-a-bucket.mdx +++ b/pages/object-storage/how-to/upload-files-into-a-bucket.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' -This page explains how to upload files into an Object Storage bucket using the [Scaleway console](https://consol.scaleway.com). To upload an object using the Amazon S3 API, refer to the [dedicated documentation](/object-storage/api-cli/object-operations/#putobject). +This page explains how to upload files into an Object Storage bucket using the [Scaleway console](https://console.scaleway.com). To upload an object using the Amazon S3 API, refer to the [dedicated documentation](/object-storage/api-cli/object-operations/#putobject). diff --git a/pages/organizations-and-projects/how-to/create-ssh-key.mdx b/pages/organizations-and-projects/how-to/create-ssh-key.mdx index 4c4e4120e9..23e55deb8e 100644 --- a/pages/organizations-and-projects/how-to/create-ssh-key.mdx +++ b/pages/organizations-and-projects/how-to/create-ssh-key.mdx @@ -149,7 +149,7 @@ You must upload the content of the public part of the SSH key pair you just gene Check if you are in the right Project before proceeding. You can check your current Organization and Project in the top-left corner of the Scaleway console. If you wish to change your Project, click the current Project name in the breadcrumb navigation and select a different existing Project in the drop-down. Click **Create Project** to create a new one. - + 2. Click **+ Add SSH key**. A popup displays. diff --git a/pages/public-gateways/how-to/upgrade-public-gateway.mdx b/pages/public-gateways/how-to/upgrade-public-gateway.mdx index 4fa8c7fb4c..9a035faada 100644 --- a/pages/public-gateways/how-to/upgrade-public-gateway.mdx +++ b/pages/public-gateways/how-to/upgrade-public-gateway.mdx @@ -15,7 +15,7 @@ This page shows you how to upgrade your Public Gateway to a superior offer type, - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) that is not already a PGW-XL (the most powerful offer type availble). +- [Created a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) that is not already a PGW-XL (the most powerful offer type available). 1. Click **Public Gateways** in the **Network** section of the side menu. 2. Click the Public Gateway you want to upgrade. Its **Overview** dashboard displays. diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index d50dc90693..53bdb3f696 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -265,7 +265,7 @@ A queue trigger is a mechanism that connects a container to a queue created with For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter. The container can then process the message, and perform any required actions, such as updating a database or sending a notification. -Refer to the [dedicated documenation](/serverless-containers/how-to/add-trigger-to-a-container/) for more information on how to add triggers to a Serverless Container. +Refer to the [dedicated documentation](/serverless-containers/how-to/add-trigger-to-a-container/) for more information on how to add triggers to a Serverless Container. ### NATS trigger diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx index d017df33c6..4c15b216e6 100644 --- a/pages/serverless-containers/reference-content/containers-limitations.mdx +++ b/pages/serverless-containers/reference-content/containers-limitations.mdx @@ -109,7 +109,7 @@ Image target platform must be: `linux/amd64`. For example, if you build an image using an ARM CPU, such as Apple silicon M series, your image will be in the `arm64` architecture, and you will have an error message during deployment. -You must ensure that you build your image to target `amd64` architecture, to acheive this there are multiple solutions: +You must ensure that you build your image to target `amd64` architecture, to achieve this there are multiple solutions: * You can use the following Docker command: `docker build --platform linux/amd64 .`, or * You can use an Instance with `amd64` architecture to run your builds. diff --git a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx index 100e633fdd..c75815fc97 100644 --- a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx +++ b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx @@ -60,7 +60,7 @@ Deploying your first service to Serverless Containers is straightforward. Here 1. **Containerize your application**: If you haven't already, package your application into a container image using a Dockerfile. -2. **Push your image to a registry**: Follow the [dedicated Quickstart documenation](/container-registry/quickstart/) to discover how to log in to the Scaleway Container Registry and store your images. +2. **Push your image to a registry**: Follow the [dedicated Quickstart documentation](/container-registry/quickstart/) to discover how to log in to the Scaleway Container Registry and store your images. 3. **Deploy your container**: Read the [How to deploy a container](/serverless-containers/how-to/deploy-container/) page to create your container using the Scaleway console. diff --git a/pages/serverless-containers/troubleshooting/container-error-state.mdx b/pages/serverless-containers/troubleshooting/container-error-state.mdx index d709a59bc3..65b70ac1fd 100644 --- a/pages/serverless-containers/troubleshooting/container-error-state.mdx +++ b/pages/serverless-containers/troubleshooting/container-error-state.mdx @@ -25,7 +25,7 @@ There are several factors that can put Serverless Containers in an error state: - Make sure your image embarks a webserver (nginx, Apache, Alpine, etc.) that can process HTTP requests. -- Make sure you specified the correct platform when building your image locally using the `--platofrm linux/amd64` argument, as Serverless Containers do not handle images built for `arm64` platforms. +- Make sure you specified the correct platform when building your image locally using the `--platform linux/amd64` argument, as Serverless Containers do not handle images built for `arm64` platforms. - Make sure your deployment does not exceed the [Serverless Containers limitations](/serverless-containers/reference-content/containers-limitations/). diff --git a/pages/serverless-containers/troubleshooting/http1-errors.mdx b/pages/serverless-containers/troubleshooting/http1-errors.mdx index 25eccd9226..ea2b9a2da6 100644 --- a/pages/serverless-containers/troubleshooting/http1-errors.mdx +++ b/pages/serverless-containers/troubleshooting/http1-errors.mdx @@ -1,7 +1,7 @@ --- title: Solving HTTP/1.0 issues description: This page provides solutions to issues encountered while using HTTP/1.0 with Scaleway Serverless Containers -tags: issues error protocol http1.0 http0.9 backwards compatibiliy +tags: issues error protocol http1.0 http0.9 backwards compatibility dates: validation: 2025-08-25 posted: 2025-08-25 diff --git a/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx b/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx index 83dd5b4017..d1d8f022b3 100644 --- a/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx +++ b/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx @@ -19,7 +19,7 @@ Testing **Private** Serverless Containers is not possible using the Scaleway con - Change the visibility of your function to **public**. Public containers can be executed anonymously. -- Make sure you have created an [authentication token](/serverless-containers/how-to/create-auth-token-from-console/) for your private function, then exexute a `curl` request from a terminal, as shown below: +- Make sure you have created an [authentication token](/serverless-containers/how-to/create-auth-token-from-console/) for your private function, then execute a `curl` request from a terminal, as shown below: ```bash curl -H "X-Auth-Token: " \ ``` \ No newline at end of file diff --git a/pages/serverless-functions/troubleshooting/http1-errors.mdx b/pages/serverless-functions/troubleshooting/http1-errors.mdx index 3c21bde815..64a03ed4b1 100644 --- a/pages/serverless-functions/troubleshooting/http1-errors.mdx +++ b/pages/serverless-functions/troubleshooting/http1-errors.mdx @@ -1,7 +1,7 @@ --- title: Solving HTTP/1.0 issues description: This page provides solutions to issues encountered while using HTTP/1.0 with Scaleway Serverless Functions -tags: issues error protocol http1.0 http0.9 backwards compatibiliy +tags: issues error protocol http1.0 http0.9 backwards compatibility dates: validation: 2025-08-25 posted: 2025-08-25 diff --git a/pages/serverless-jobs/troubleshooting/job-startup-command-fails.mdx b/pages/serverless-jobs/troubleshooting/job-startup-command-fails.mdx index 66c78c9b0d..8c88b59033 100644 --- a/pages/serverless-jobs/troubleshooting/job-startup-command-fails.mdx +++ b/pages/serverless-jobs/troubleshooting/job-startup-command-fails.mdx @@ -1,7 +1,7 @@ --- title: My job run fails when executing the startup command description: Troubleshoot job run failures due to startup commands for your Scaleway Serverless Jobs. -tags: serverless jobs troubleshooting issue error state message fail execution log faliure does not run command +tags: serverless jobs troubleshooting issue error state message fail execution log failure does not run command dates: validation: 2025-08-20 posted: 2025-08-20 @@ -13,7 +13,7 @@ My job run fails due to its startup command. ## Cause -Complex commands, such as piped or `xargs` commands may lead to failures due to techical limitations of Serverless Jobs. +Complex commands, such as piped or `xargs` commands may lead to failures due to technical limitations of Serverless Jobs. ## Possible solutions diff --git a/pages/serverless-sql-databases/api-cli/secure-connection-ssl-tls.mdx b/pages/serverless-sql-databases/api-cli/secure-connection-ssl-tls.mdx index b102f5e09b..89c3e622c9 100644 --- a/pages/serverless-sql-databases/api-cli/secure-connection-ssl-tls.mdx +++ b/pages/serverless-sql-databases/api-cli/secure-connection-ssl-tls.mdx @@ -78,7 +78,7 @@ DATABASES = { 'NAME': {databasename}, 'USER': {username}, #IAM principal ID of the user or application you are connecting with 'PASSWORD': {password}, #IAM Secret Key of the user or application you are connecting with - 'HOST': {host}, #Host formated as {database-id}.pg.sdb.{region}.scw.cloud + 'HOST': {host}, #Host formatted as {database-id}.pg.sdb.{region}.scw.cloud 'PORT': {port}, #Default port for PostgreSQL is supported: 5432 'OPTIONS': { 'sslmode':'verify-full', @@ -110,7 +110,7 @@ conn = await asyncpg.connect("postgresql://{username}:{password}@{host}:{port}/{ To ensure SSL/TLS is enforced and your server certificate is valid, add `ssl:true` to your connection parameters: ```js const client = new Client({ - host: {host}, //Host formated as {database-id}.pg.sdb.{region}.scw.cloud + host: {host}, //Host formatted as {database-id}.pg.sdb.{region}.scw.cloud port: {port}, //Default port for PostgreSQL is supported: 5432 database: {databasename}, user: {username}, //IAM principal ID of the user or application you are connecting with @@ -127,7 +127,7 @@ To ensure SSL/TLS is enforced and the server certificate is valid, edit your con ```js const sql = postgres({ - host: {host}, //Host formated as {database-id}.pg.sdb.{region}.scw.cloud + host: {host}, //Host formatted as {database-id}.pg.sdb.{region}.scw.cloud port: {port}, //Default port for PostgreSQL is supported: 5432 database: {databasename}, user: {username}, //IAM principal ID of the user or application you are connecting with diff --git a/pages/serverless-sql-databases/troubleshooting/failing-backup-restore.mdx b/pages/serverless-sql-databases/troubleshooting/failing-backup-restore.mdx index 850d0407d2..78d2a21c10 100644 --- a/pages/serverless-sql-databases/troubleshooting/failing-backup-restore.mdx +++ b/pages/serverless-sql-databases/troubleshooting/failing-backup-restore.mdx @@ -38,7 +38,7 @@ These issues are caused by queries locking database rows (usually long running t To solve these issues, stop these queries: -- List PostgreSQL processes and identify the ones that have been running transactions since several hours ('xact_start' colmun) with the following command: +- List PostgreSQL processes and identify the ones that have been running transactions since several hours ('xact_start' column) with the following command: ``` SELECT pid, state, usename, query, xact_start, query_start FROM pg_stat_activity ORDER BY xact_start; ``` diff --git a/pages/transactional-email/how-to/autoconfigure-domain.mdx b/pages/transactional-email/how-to/autoconfigure-domain.mdx index 20516c98c3..db59b0bab2 100644 --- a/pages/transactional-email/how-to/autoconfigure-domain.mdx +++ b/pages/transactional-email/how-to/autoconfigure-domain.mdx @@ -15,7 +15,7 @@ Automatic configuration of your DNS zone streamlines the setup of your domain fo You can enable autoconfiguration directly from the Scaleway console (see instructions below), through the [Transactional Email API](https://www.scaleway.com/en/developers/api/transactional-email/#path-domains-register-a-domain-in-a-project), or via [Terraform/OpenTofu](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/data-sources/tem_domain.md) using the `autoconfig` parameter (`bool`). - This documentation covers the use of DNS autoconfiguration for domains already registerd with Transactional Email. If you want to add a new domain, refer to [How to configure your sending domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/). + This documentation covers the use of DNS autoconfiguration for domains already registered with Transactional Email. If you want to add a new domain, refer to [How to configure your sending domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/). diff --git a/pages/vpc/concepts.mdx b/pages/vpc/concepts.mdx index bf7169d8fe..464b0fdfe5 100644 --- a/pages/vpc/concepts.mdx +++ b/pages/vpc/concepts.mdx @@ -85,7 +85,7 @@ When an IPv6-compatible resource is attached to a Private Network, it has a priv NACLs are currently in Public Beta, and configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console. -A VPC's Network **A**ccess **C**ontrol **L**ist is composed of stateless rules to control the flow of traffic between Private Networks. By default, the list contains no rules, and therefore traffic is allowed to flow unrestrictedly between the VPC's Private Networks. Add rules to the list to start creating restrictions. [Take a deeper dive into NACLs](/vpc/reference-content/understanding-nacls/). +A VPC's Network **A**ccess **C**control **L**ist is composed of stateless rules to control the flow of traffic between Private Networks. By default, the list contains no rules, and therefore traffic is allowed to flow unrestrictedly between the VPC's Private Networks. Add rules to the list to start creating restrictions. [Take a deeper dive into NACLs](/vpc/reference-content/understanding-nacls/). ## Private IP address @@ -126,7 +126,7 @@ Each route in a route table has a **scope**: it may be advertised across the ent ## Routing -Routing allows resources on Private Networks witin the same VPC to communicate with each other, via managed and custom routes. Routing is activated by default whenever you create a new VPC, and can be activated on pre-existing VPCs by [following these steps](/vpc/how-to/manage-routing/#how-to-activate-routing). +Routing allows resources on Private Networks within the same VPC to communicate with each other, via managed and custom routes. Routing is activated by default whenever you create a new VPC, and can be activated on pre-existing VPCs by [following these steps](/vpc/how-to/manage-routing/#how-to-activate-routing). Each routed VPC has a [route table](#route-table) which is automatically populated with routes to each of its Private Networks. When you attach a Public Gateway to a Private Network, and tell it to advertise a default route to the internet, such routes are also added to the VPC's route table. You can also create your own [custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route), to route traffic towards defined destination IP ranges towards specific "next hop" resources. diff --git a/pages/vpc/faq.mdx b/pages/vpc/faq.mdx index 481df974a5..a792f310c8 100644 --- a/pages/vpc/faq.mdx +++ b/pages/vpc/faq.mdx @@ -76,7 +76,7 @@ Technically, any Ethernet payload should work over Private Networks. However, on ### Can I connect multiple Private Networks to the same Scaleway resource? -This depends on the type of resource. For Instances and most other products, you can configure up to **8** Private Networks on the same Scaleway resource. Some resource types, such as Managed Databases and Serverlesss Functions and Containers, only support one Private Network attachment per resource. Refer to the product's documentation on Private Networks, or [Getting the most from Private Networks](/vpc/reference-content/getting-most-private-networks/#resource-specific-information) for more information. +This depends on the type of resource. For Instances and most other products, you can configure up to **8** Private Networks on the same Scaleway resource. Some resource types, such as Managed Databases and Serverless Functions and Containers, only support one Private Network attachment per resource. Refer to the product's documentation on Private Networks, or [Getting the most from Private Networks](/vpc/reference-content/getting-most-private-networks/#resource-specific-information) for more information. ### How many resources can I attach to each Private Network? diff --git a/pages/vpc/how-to/activate-dhcp.mdx b/pages/vpc/how-to/activate-dhcp.mdx index 45a1c47b9b..afe3ff8d2e 100644 --- a/pages/vpc/how-to/activate-dhcp.mdx +++ b/pages/vpc/how-to/activate-dhcp.mdx @@ -54,7 +54,7 @@ Activating DHCP will overwrite any existing manually configured static IP addres 4. Click **Activate DHCP** on the banner. The following screen displays: - + 5. Read the warning message carefully, and click **Activate DHCP** when you are ready. diff --git a/pages/vpc/quickstart.mdx b/pages/vpc/quickstart.mdx index 14a98eb145..8c120317f6 100644 --- a/pages/vpc/quickstart.mdx +++ b/pages/vpc/quickstart.mdx @@ -195,7 +195,7 @@ When your route table starts to populate, it will look something like this: For help with understanding the route table, refer to our full [routing documentation](/vpc/reference-content/understanding-routing/). For guidance on creating custom routes, see the [routing how-to](/vpc/how-to/manage-routing/#how-to-create-a-custom-route). -You can use the VPC's **N**etwork **A**ccess **C**ontrol **L**ist to limit and restrict certain routes within a VPC, but this feature is currently available via the [VPC API only](/vpc/reference-content/understanding-nacls/) only. +You can use the VPC's **N**etwork **A**ccess **C**control **L**ist to limit and restrict certain routes within a VPC, but this feature is currently available via the [VPC API only](/vpc/reference-content/understanding-nacls/) only. ## How to delete a Private Network diff --git a/pages/vpc/reference-content/understanding-nacls.mdx b/pages/vpc/reference-content/understanding-nacls.mdx index 08aa2383e4..d5e0df7eae 100644 --- a/pages/vpc/reference-content/understanding-nacls.mdx +++ b/pages/vpc/reference-content/understanding-nacls.mdx @@ -15,7 +15,7 @@ import image3 from './assets/scaleway-nacl-example.webp' NACLs are currently in Public Beta, and configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console. -Every VPC has a Network **A**ccess **C**ontrol **L**ist (NACL). This list is composed of stateless rules to control the flow of traffic between the Private Networks of the VPC. By default, at first, the list contains no rules, and therefore traffic is allowed to flow unrestrictedly. You can add rules to restrict traffic flow according to your requirements. +Every VPC has a Network **A**ccess **C**control **L**ist (NACL). This list is composed of stateless rules to control the flow of traffic between the Private Networks of the VPC. By default, at first, the list contains no rules, and therefore traffic is allowed to flow unrestrictedly. You can add rules to restrict traffic flow according to your requirements. This document sets out general information and best practices about Scaleway VPC NACLs. diff --git a/pages/vpc/reference-content/understanding-routing.mdx b/pages/vpc/reference-content/understanding-routing.mdx index 27a40f1d60..e7c4bcd8e3 100644 --- a/pages/vpc/reference-content/understanding-routing.mdx +++ b/pages/vpc/reference-content/understanding-routing.mdx @@ -42,7 +42,7 @@ Every VPC has an associated **route table**, used to manage and control the rout - For custom routes, the next hop is a defined resource on a defined Private Network. - If the destination IP is not known on the VPC (represented by the `0.0.0.0/0` address), its next hop will be a Public Gateway so that it can reach the public internet (as long as a Public Gateway set to advertise the default route has been attached to the Private Network). - A **description**. This helps to describe the type of route, e.g. `Local subnet route` for routes to Private Networks, or `Default route to internet` for routes to Public Gateways, or a user-defined description for custom routes. -- A **scope**. This shows whether teh route is advertised across the entire VPC, or (in the case of default routes), only certain Private Networks. +- A **scope**. This shows whether the route is advertised across the entire VPC, or (in the case of default routes), only certain Private Networks. When deciding which route to apply, the route table reads the routes from most specific to least specific, in terms of destination IP range. The first matching route encountered is the one that determines the path for the traffic. Therefore, a route to destination `172.16.8.0/22` is applied before a default route to `0.0.0.0/0`. diff --git a/pages/webhosting/how-to/manage-ftp-accounts.mdx b/pages/webhosting/how-to/manage-ftp-accounts.mdx index d6a7e3d8d6..ada37725d6 100644 --- a/pages/webhosting/how-to/manage-ftp-accounts.mdx +++ b/pages/webhosting/how-to/manage-ftp-accounts.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' -FTP (File Transfer Protocol) is used to tranfer data from your computer to your Web Hosting account and vice versa. This allows you to manage the content of your website. +FTP (File Transfer Protocol) is used to transfer data from your computer to your Web Hosting account and vice versa. This allows you to manage the content of your website. You can create and manage FTP accounts directly from the Scaleway console. diff --git a/pages/webhosting/how-to/manage-wordpress-webhosting.mdx b/pages/webhosting/how-to/manage-wordpress-webhosting.mdx index cd2a132b03..3834cd0b4d 100644 --- a/pages/webhosting/how-to/manage-wordpress-webhosting.mdx +++ b/pages/webhosting/how-to/manage-wordpress-webhosting.mdx @@ -34,7 +34,7 @@ This page shows you how to access WordPress, create a mailbox, access your WordP 3. Enter a strong password. 4. Enter your email address in the **Your Email** field. 5. Optionally, tick the box to discourage search engines from indexing your website or leave it as is. -6. Click **Install WordPress**. The **Sucess** page displays. +6. Click **Install WordPress**. The **Success** page displays. 7. Click **Log in** et log in using your credentials. Your WordPress hosting dashboard displays. diff --git a/pages/webhosting/how-to/protect-webhosting.mdx b/pages/webhosting/how-to/protect-webhosting.mdx index a928523b78..e09335819d 100644 --- a/pages/webhosting/how-to/protect-webhosting.mdx +++ b/pages/webhosting/how-to/protect-webhosting.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' -The [protected hosting](/webhosting/concepts/#protected-hosting) feature is designed to prevent any accidental or unauthorized deletions of your Web Hosting plan. When enabled, this feature ensures that your Web Hosting plan cannot be deleted, providing an extra layer of protection against unintended disruptions. This is particularly useful for preventing errors, such as accidental cancelations during routine maintenance or management activities. +The [protected hosting](/webhosting/concepts/#protected-hosting) feature is designed to prevent any accidental or unauthorized deletions of your Web Hosting plan. When enabled, this feature ensures that your Web Hosting plan cannot be deleted, providing an extra layer of protection against unintended disruptions. This is particularly useful for preventing errors, such as accidental cancellations during routine maintenance or management activities. diff --git a/tutorials/access-mac-mini-with-reemo/index.mdx b/tutorials/access-mac-mini-with-reemo/index.mdx index 23fc347629..abf6563056 100644 --- a/tutorials/access-mac-mini-with-reemo/index.mdx +++ b/tutorials/access-mac-mini-with-reemo/index.mdx @@ -62,13 +62,13 @@ In this tutorial, you will learn how to launch your Mac mini development environ ## Installing the Reemo client -1. Log into your Mac mini using an exsiting [remote desktop connection](/apple-silicon/how-to/access-remote-desktop-mac-mini/). +1. Log into your Mac mini using an existing [remote desktop connection](/apple-silicon/how-to/access-remote-desktop-mac-mini/). 2. Open a terminal once logged into your Mac mini, open a terminal. 3. Run the following command to install the Reemo client on your machine: ```bash # For older MacOS version (pre ventura) you can install this audio driver for audio capture support brew install blackhole-2ch - # You need Administrator Priviledges + # You need Administrator Privileges curl -skL -o /tmp/install_reemo.x 'https://download.reemo.io/macos/setup.x' && sudo bash /tmp/install_reemo.x ``` diff --git a/tutorials/ansible-bionic-beaver/index.mdx b/tutorials/ansible-bionic-beaver/index.mdx index 3268c51604..ccd6b93de7 100644 --- a/tutorials/ansible-bionic-beaver/index.mdx +++ b/tutorials/ansible-bionic-beaver/index.mdx @@ -41,7 +41,7 @@ Ansible works by configuring client machines from a computer that has the Ansibl If you do not know your server IP, you can list your existing servers using `scw ps` (Scaleway CLI). For more information on the Scaleway CLI, refer to the tutorial on the [Scaleway Command Line Interface](https://www.scaleway.com/docs/manage-cloud-servers-with-scaleway-cli/). - The server IP can also be retrieved from the Scaleway console. Once logged in, check the **IP Adresses** in the **Servers** tab of the left menu. + The server IP can also be retrieved from the Scaleway console. Once logged in, check the **IP Addresses** in the **Servers** tab of the left menu. If you use the root user, you can remove the `sudo` before each command. diff --git a/tutorials/configure-apache-lets-encrypt/index.mdx b/tutorials/configure-apache-lets-encrypt/index.mdx index e0f46c1749..e66cf25569 100644 --- a/tutorials/configure-apache-lets-encrypt/index.mdx +++ b/tutorials/configure-apache-lets-encrypt/index.mdx @@ -64,7 +64,7 @@ We will walk you through the process of setting up a website on Apache and obtai

New Website

-

This is the new website of myweb.exaple.com

+

This is the new website of myweb.example.com

``` diff --git a/tutorials/configure-nodemcu-iot-hub/index.mdx b/tutorials/configure-nodemcu-iot-hub/index.mdx index 7d5035b4ac..784315c7a2 100644 --- a/tutorials/configure-nodemcu-iot-hub/index.mdx +++ b/tutorials/configure-nodemcu-iot-hub/index.mdx @@ -290,7 +290,7 @@ Next, we will use our NodeMCU device to measure temperature and humidity and pub // Initialize DHT sensor. DHT dht(DHTPin, DHTTYPE); - // Timers auxiliar variables + // Timers auxiliary variables long now = millis(); long lastMeasure = 0; diff --git a/tutorials/configure-virtual-machine-esxi/index.mdx b/tutorials/configure-virtual-machine-esxi/index.mdx index fa949b1271..cccfc367ba 100644 --- a/tutorials/configure-virtual-machine-esxi/index.mdx +++ b/tutorials/configure-virtual-machine-esxi/index.mdx @@ -120,7 +120,7 @@ The VMware ESXi hypervisor uses full virtualization for virtual machines. They c Choose the settings according to your guest operating system. For Ubuntu Linux go with the following settings: - - **Compatability**: `ESXi 7.0 virtual machine` + - **Compatibility**: `ESXi 7.0 virtual machine` - **Guest OS family**: `Linux` - **Guest OS version**: `Ubuntu Linux (64-bit)` 4. Select the datastore in which to store the configuration and disk files: diff --git a/tutorials/create-models-django/index.mdx b/tutorials/create-models-django/index.mdx index 442b67178b..6d0f4cee66 100644 --- a/tutorials/create-models-django/index.mdx +++ b/tutorials/create-models-django/index.mdx @@ -203,7 +203,7 @@ Now that your environment (`my-django`) is set up, we can create a new applicati def __str__(self): return self.choice_text ``` -4. Save these changes and start a new Python interactive shell by running the following commnand: +4. Save these changes and start a new Python interactive shell by running the following command: ``` python manage.py shell ``` diff --git a/tutorials/deploy-istio-kapsule-proxy-protocol/index.mdx b/tutorials/deploy-istio-kapsule-proxy-protocol/index.mdx index afdb984857..8d89fad2ed 100644 --- a/tutorials/deploy-istio-kapsule-proxy-protocol/index.mdx +++ b/tutorials/deploy-istio-kapsule-proxy-protocol/index.mdx @@ -42,7 +42,7 @@ This tutorial describes the steps required to deploy Istio on a Scaleway Kuberne kubectl create namespace istio-system ``` -3. Install the Istio base and control plane into the previously created namesapce: +3. Install the Istio base and control plane into the previously created namespace: ``` helm install istio-base istio/base -n istio-system diff --git a/tutorials/deploy-nextcloud-s3/index.mdx b/tutorials/deploy-nextcloud-s3/index.mdx index 76bc199ed6..8b07e2fa39 100644 --- a/tutorials/deploy-nextcloud-s3/index.mdx +++ b/tutorials/deploy-nextcloud-s3/index.mdx @@ -59,7 +59,7 @@ Combining NextCloud with Scaleway Object Storage gives you infinite storage spac Check the [NextCloud changelog](https://nextcloud.com/changelog/) for the latest release. -5. Download `bzip2` to exract the archive. +5. Download `bzip2` to extract the archive. ``` apt install bzip2 ``` diff --git a/tutorials/deploy-wordpress-managed-database-mysql8/index.mdx b/tutorials/deploy-wordpress-managed-database-mysql8/index.mdx index d62702d46d..2164feb08a 100644 --- a/tutorials/deploy-wordpress-managed-database-mysql8/index.mdx +++ b/tutorials/deploy-wordpress-managed-database-mysql8/index.mdx @@ -200,7 +200,7 @@ By default, HTTP is a plain text protocol and does not use any encryption. To se new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 <-- Type 2 to redirect all HTTP connections to HTTPS, type 1 to your vistors decide if they want to use HTTP or HTTPS. Confirm your choice by pressing Enter + Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 <-- Type 2 to redirect all HTTP connections to HTTPS, type 1 to your visitors decide if they want to use HTTP or HTTPS. Confirm your choice by pressing Enter Enabled Apache rewrite module Redirecting vhost in /etc/apache2/sites-enabled/blog.example.com.conf to ssl vhost in /etc/apache2/sites-available/blog.example.com-le-ssl.conf diff --git a/tutorials/discourse-forum/index.mdx b/tutorials/discourse-forum/index.mdx index 63f2080a4a..0831ca9e48 100644 --- a/tutorials/discourse-forum/index.mdx +++ b/tutorials/discourse-forum/index.mdx @@ -46,7 +46,7 @@ For those looking to set up Discourse, using the official [Docker image](https:/ 1. Log into your Instance using [SSH](/instances/how-to/connect-to-instance/). 2. Update the `apt` package cache and upgrade the software already installed on the Instance to the latest version available in Ubuntu's repositories: ``` - apt update && apt ugprade -y + apt update && apt upgrade -y ``` 3. Install packages required for Discourse: ``` diff --git a/tutorials/first-steps-linux-command-line/index.mdx b/tutorials/first-steps-linux-command-line/index.mdx index dff8de8366..d4db5085a6 100644 --- a/tutorials/first-steps-linux-command-line/index.mdx +++ b/tutorials/first-steps-linux-command-line/index.mdx @@ -479,7 +479,7 @@ When creating user accounts, you need to either be logged in as `root`, or else sudo usermod -aG sudo sarah ``` -3. Log in as the new user with the `su` (**s**witch **u**ser) command: +3. Log in as the new user with the `su` (**s**witch **U**ser) command: ``` su sarah diff --git a/tutorials/get-started-python/index.mdx b/tutorials/get-started-python/index.mdx index a3b8bff64c..cc99a2646d 100644 --- a/tutorials/get-started-python/index.mdx +++ b/tutorials/get-started-python/index.mdx @@ -46,7 +46,7 @@ To download Anaconda (and benefit from the Python interpreter plus these extra f ## 2: Getting ready to code: opening the Python Interactive Shell -We will be coding from the **terminal**, also referred to as the **command line** or **C**ommand **L**ine **I**nterface. We'll start off by using the **Python Interactive Shell**, which is great for testing quick snippets of code. Later, we'll show how you can write and save all your code in a text file, and just use the terminal to run the code. +We will be coding from the **terminal**, also referred to as the **command line** or **C**ommand **L**ine **I**nterface. We'll start off by using the **Python Interactive Shell**, which is great for testing quick snippets of code. Later, we'll show how you can write and save all your code in a text file, and just use the terminal to run the code. 1. Open the **terminal** on your computer. diff --git a/tutorials/hestiacp/index.mdx b/tutorials/hestiacp/index.mdx index dd75ffdcdb..fb6656280a 100644 --- a/tutorials/hestiacp/index.mdx +++ b/tutorials/hestiacp/index.mdx @@ -113,7 +113,7 @@ In this tutorial, you will learn how to install and configure HestiaCP on Ubuntu Note: Automatic updates are enabled by default. If you would like to disable them, please log in and navigate to Server > Updates to turn them off. - Help support the Hestia Contol Panel project by donating via PayPal: + Help support the Hestia Control Panel project by donating via PayPal: https://www.hestiacp.com/donate -- Sincerely yours, diff --git a/tutorials/host-github-runner/index.mdx b/tutorials/host-github-runner/index.mdx index bd6b43321b..3bcb9ccf97 100644 --- a/tutorials/host-github-runner/index.mdx +++ b/tutorials/host-github-runner/index.mdx @@ -26,7 +26,7 @@ GitHub Actions stands as a versatile tool, simplifying the automation of all you GitHub offers a limited range of complementary resources for constructing applications through GitHub Actions; however, proficient developers can swiftly encounter these constraints. Teams engaged in professional-grade projects might also want full authority over their build environment. GitHub extends the option to use runners on self-managed instances. A runner function is an application executing tasks from a GitHub Actions workflow. -In this guide, you will learn how to configure a GitHub Actions runner on a Scaleway Instance, effectively streamlining your project workflows. For typical workloads, opting for a [General Purpose Instance with shared resources](/instances/reference-content/choosing-instance-type/) is recommended. For resource-intensive workloads, the use of General Purpose Instances with dedicated resouces provides enhanced performance. +In this guide, you will learn how to configure a GitHub Actions runner on a Scaleway Instance, effectively streamlining your project workflows. For typical workloads, opting for a [General Purpose Instance with shared resources](/instances/reference-content/choosing-instance-type/) is recommended. For resource-intensive workloads, the use of General Purpose Instances with dedicated resources provides enhanced performance. We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/hosting-nextjs-webapp-serverless-containers/index.mdx b/tutorials/hosting-nextjs-webapp-serverless-containers/index.mdx index 8d4f6163d3..a27fa7dab5 100644 --- a/tutorials/hosting-nextjs-webapp-serverless-containers/index.mdx +++ b/tutorials/hosting-nextjs-webapp-serverless-containers/index.mdx @@ -26,7 +26,7 @@ import Requirements from '@macros/iam/requirements.mdx' - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Installed [Docker](https://docs.docker.com/get-started/get-docker/) or [Docker Egine](https://docs.docker.com/engine/install/) +- Installed [Docker](https://docs.docker.com/get-started/get-docker/) or [Docker Engine](https://docs.docker.com/engine/install/) - [Created a Scaleway Container Registry namespace](/container-registry/how-to/create-namespace/) and [logged into it](/container-registry/how-to/connect-docker-cli/) ## Create and host a basic Next.js web application diff --git a/tutorials/hosting-static-websites-serverless-containers/index.mdx b/tutorials/hosting-static-websites-serverless-containers/index.mdx index c86e6366d2..a3284a8294 100644 --- a/tutorials/hosting-static-websites-serverless-containers/index.mdx +++ b/tutorials/hosting-static-websites-serverless-containers/index.mdx @@ -25,7 +25,7 @@ import Requirements from '@macros/iam/requirements.mdx' - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Installed [Docker](https://docs.docker.com/get-started/get-docker/) or [Docker Egine](https://docs.docker.com/engine/install/) +- Installed [Docker](https://docs.docker.com/get-started/get-docker/) or [Docker Engine](https://docs.docker.com/engine/install/) - [Created a Scaleway Container Registry namespace](/container-registry/how-to/create-namespace/) and [logged into it](/container-registry/how-to/connect-docker-cli/) ## Create and host a simple HTML static page diff --git a/tutorials/lb-firewall-haproxy-pfsense/index.mdx b/tutorials/lb-firewall-haproxy-pfsense/index.mdx index db9a666e9c..91c213a40a 100644 --- a/tutorials/lb-firewall-haproxy-pfsense/index.mdx +++ b/tutorials/lb-firewall-haproxy-pfsense/index.mdx @@ -482,7 +482,7 @@ With this, we delegate lifecycle management of the failover IP to CARP, by tweak "https://api.online.net/api/v1/server/failover/edit" | tee /root/carp.log fi elif [ "$INTERFACE" == "1@igb1.2001" ]; then - # Retreive main IP FO + # Retrieve main IP FO if [ "$STATUS" == "MASTER" ]; then FAILOVER_IP=$PF1_IPFO DESTINATION_IP=$PF1_IP @@ -540,7 +540,7 @@ With this, we delegate lifecycle management of the failover IP to CARP, by tweak "https://api.online.net/api/v1/server/failover/edit" | tee /root/carp.log fi elif [ "$INTERFACE" == "2@igb1.2001" ]; then - # Retreive main IP FO + # Retrieve main IP FO if [ "$STATUS" == "MASTER" ]; then FAILOVER_IP=$PF2_IPFO DESTINATION_IP=$PF2_IP diff --git a/tutorials/librenms-monitoring/index.mdx b/tutorials/librenms-monitoring/index.mdx index 1c428c87be..05ca98aae9 100644 --- a/tutorials/librenms-monitoring/index.mdx +++ b/tutorials/librenms-monitoring/index.mdx @@ -39,7 +39,7 @@ The software is based on PHP and MySQL (MariaDB) and is a community-based fork o ## Installing LibreNMS -1. Update the apt package cache and upgrate the already installed system packages: +1. Update the apt package cache and upgrade the already installed system packages: ``` apt update && apt upgrade -y ``` diff --git a/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx b/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx index 3b9b72bc96..f66297bf5c 100644 --- a/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx +++ b/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx @@ -98,7 +98,7 @@ Create or clone your virtual machines on both servers of the cluster to distribu * The backend port * (Optionally) The proxy protocol to use * The healh check information - * The IP addreses of your VM's inside the Private Network + * The IP addresses of your VM's inside the Private Network For more information about the front and backend configuration, refer to the [Load Balancers documentation](/load-balancer/how-to/manage-frontends-and-backends/). diff --git a/tutorials/mongodb-ubuntu-1604/index.mdx b/tutorials/mongodb-ubuntu-1604/index.mdx index d5c0763243..f81c0c0a86 100644 --- a/tutorials/mongodb-ubuntu-1604/index.mdx +++ b/tutorials/mongodb-ubuntu-1604/index.mdx @@ -310,7 +310,7 @@ Uncomplicated Firewall (UFW), is a front-end to iptables. Its main goal is to ma ### Configuring a public bindIP -1. To allow remote connections, add our host's publically routable IP address to the `mongod.conf` file. +1. To allow remote connections, add our host's publicly routable IP address to the `mongod.conf` file. ``` nano /etc/mongod.conf ``` diff --git a/tutorials/openvpn-instant-app/index.mdx b/tutorials/openvpn-instant-app/index.mdx index 9a558de39d..20a75f3b89 100644 --- a/tutorials/openvpn-instant-app/index.mdx +++ b/tutorials/openvpn-instant-app/index.mdx @@ -103,7 +103,7 @@ Read our tutorial: https://www.scaleway.com/en/docs/tutorials/openvpn-instant-ap starts an HTTP server you can download your openvpn client configuration from scw-ovpn add-instance PROTOCOL PORT ID - add an openvpn instance listenning on PORT with PROTOCOL. + add an openvpn instance listening on PORT with PROTOCOL. protocol must be one of udp and tcp. scw-ovpn del-instance ID diff --git a/tutorials/overleaf/index.mdx b/tutorials/overleaf/index.mdx index 3470cd0a03..8203f4609e 100644 --- a/tutorials/overleaf/index.mdx +++ b/tutorials/overleaf/index.mdx @@ -137,7 +137,7 @@ It is particularly favored by academics and professionals for producing scientif ``` - Replace `sharelatex` with the name of the Share LateX container. Use `docker ps` to find it. - - The installation of `textlive` may take a while and take up a lot of storage space. Ensure your Instance has sufficent storage available. + - The installation of `textlive` may take a while and take up a lot of storage space. Ensure your Instance has sufficient storage available. ## Configuring SSL diff --git a/tutorials/python-for-loops/index.mdx b/tutorials/python-for-loops/index.mdx index 3f03b6beaa..9d203c2934 100644 --- a/tutorials/python-for-loops/index.mdx +++ b/tutorials/python-for-loops/index.mdx @@ -558,7 +558,7 @@ print(c_words) -It is **bad practice** to modify a list (or dictionary, or any other sequence) while you are iterating over it. For example, we could try to achieve the above task by removing words in the list when they do not start with **c**, but as words are removed mid-loop, the length of the list changes and this confuses the iterator, which ends up missing out some words as according to their index postion, they have already been checked. The output would therefore be inaccurate. +It is **bad practice** to modify a list (or dictionary, or any other sequence) while you are iterating over it. For example, we could try to achieve the above task by removing words in the list when they do not start with **c**, but as words are removed mid-loop, the length of the list changes and this confuses the iterator, which ends up missing out some words as according to their index position, they have already been checked. The output would therefore be inaccurate. For this reason, you should always follow the example above, and use separate variables to collect data from the sequence you are iterating over. diff --git a/tutorials/set-up-yunohost-debian/index.mdx b/tutorials/set-up-yunohost-debian/index.mdx index cecb43b737..a9e1b8abaf 100644 --- a/tutorials/set-up-yunohost-debian/index.mdx +++ b/tutorials/set-up-yunohost-debian/index.mdx @@ -63,7 +63,7 @@ Yunohost is an open-source solution designed for the administration of a persona - https:/// (global IP, if you're on a VPS) If this is your first time with YunoHost, it is strongly recommended to take - time to read the administator documentation and in particular the sections + time to read the administrator documentation and in particular the sections 'Finalizing your setup' and 'Getting to know YunoHost'. It is available at the following URL : https://yunohost.org/admindoc =============================================================================== diff --git a/tutorials/setup-mongodb-on-ubuntu/index.mdx b/tutorials/setup-mongodb-on-ubuntu/index.mdx index 786202d0fa..9c48e41499 100644 --- a/tutorials/setup-mongodb-on-ubuntu/index.mdx +++ b/tutorials/setup-mongodb-on-ubuntu/index.mdx @@ -325,7 +325,7 @@ Uncomplicated Firewall (UFW), is a front-end to iptables. Its main goal is to ma ### Configuring a public bindIP -1. To allow remote connections, add the host's publically routable IP address to the `mongod.conf` file. +1. To allow remote connections, add the host's publicly routable IP address to the `mongod.conf` file. ``` nano /etc/mongod.conf ``` diff --git a/tutorials/setup-postfix-ubuntu-bionic/index.mdx b/tutorials/setup-postfix-ubuntu-bionic/index.mdx index e53da57cf9..0dd9da7ff0 100644 --- a/tutorials/setup-postfix-ubuntu-bionic/index.mdx +++ b/tutorials/setup-postfix-ubuntu-bionic/index.mdx @@ -255,7 +255,7 @@ You learn also how to install a Roundcube webmail interface to be able to read y ``` Add the output as a `TXT` record to your domain's DNS zone to publish your DKIM public key in DNS. - Refer to [How to manage DNS records](/domains-and-dns/how-to/manage-dns-records/) for furher information. + Refer to [How to manage DNS records](/domains-and-dns/how-to/manage-dns-records/) for further information. ## Install Roundcube Webmail diff --git a/tutorials/sns-instances-notification-system/index.mdx b/tutorials/sns-instances-notification-system/index.mdx index 8b1e5dc3a4..656c955060 100644 --- a/tutorials/sns-instances-notification-system/index.mdx +++ b/tutorials/sns-instances-notification-system/index.mdx @@ -183,7 +183,7 @@ We continue to add to our `main.tf` file to create the subscriber and publisher ``` resource "scaleway_instance_server" "subscriber_sns_tuto_instance" { project_id = scaleway_account_project.sns_tutorial.id - name = "suscriber-server" + name = "subscriber-server" type = "PLAY2-PICO" image = "debian_bookworm" ip_id = scaleway_instance_ip.subscriber_public_ip.id diff --git a/tutorials/terraform-quickstart/assets/scaleway-terraform-schema.svg b/tutorials/terraform-quickstart/assets/scaleway-terraform-schema.svg index 11f427e5fd..191b79241b 100644 --- a/tutorials/terraform-quickstart/assets/scaleway-terraform-schema.svg +++ b/tutorials/terraform-quickstart/assets/scaleway-terraform-schema.svg @@ -1,3 +1,3 @@ -
Terraform
Terraform
Scaleway Provider
Scaleway Provider
main.tf
main....
Configuration files
Confi...
Your Local Machine
Your Local Machine
Scaleway Cloud
Scaleway Cloud
Virtual Cloud Instances
Virtual Cloud Instances
Elastic Metal servers
Elastic Metal Ser...
Terraform Infrastructure
Terraform Infrastructu...
Configures
Configures
Manages
ManagesViewer does not support full SVG 1.1 \ No newline at end of file +
Terraform
Terraform
Scaleway Provider
Scaleway Provider
main.tf
main....
Configuration files
Confi...
Your Local Machine
Your Local Machine
Scaleway Cloud
Scaleway Cloud
Virtual Cloud Instances
Virtual Cloud Instances
Elastic Metal servers
Elastic Metal Set...
Terraform Infrastructure
Terraform Infrastructu...
Configures
Configures
Manages
ManagesViewer does not support full SVG 1.1 \ No newline at end of file diff --git a/tutorials/upgrade-managed-postgresql-database/index.mdx b/tutorials/upgrade-managed-postgresql-database/index.mdx index d60f60c86c..ae4bf5b94c 100644 --- a/tutorials/upgrade-managed-postgresql-database/index.mdx +++ b/tutorials/upgrade-managed-postgresql-database/index.mdx @@ -219,7 +219,7 @@ This solution enables you to migrate your database(s) automatically, with a bash } # Get the instance major version - instance_major_verion () { + instance_major_version () { run_rdb_cli instance get "$1" | jq -r .engine | awk -F'-' '{print $2}' | awk -F'.' '{print $1}' } @@ -262,7 +262,7 @@ This solution enables you to migrate your database(s) automatically, with a bash done } - # Check if instance_id exists and is reacheable with current cli configuration + # Check if instance_id exists and is reachable with current cli configuration check_instance () { if [ "$1" = "" ]; then log_error "You must specify an instance_id" @@ -303,8 +303,8 @@ This solution enables you to migrate your database(s) automatically, with a bash check_instance "$new_instance" # Check instance versions - old_major_version=$(instance_major_verion "$old_instance") - new_major_version=$(instance_major_verion "$new_instance") + old_major_version=$(instance_major_version "$old_instance") + new_major_version=$(instance_major_version "$new_instance") if [ "$old_major_version" -ge "$new_major_version" ]; then log_error "New instance major version must be superior to the old one"; exit 1 diff --git a/tutorials/zabbix-monitoring/index.mdx b/tutorials/zabbix-monitoring/index.mdx index e37b4c2f4f..354153849a 100644 --- a/tutorials/zabbix-monitoring/index.mdx +++ b/tutorials/zabbix-monitoring/index.mdx @@ -81,7 +81,7 @@ Data of the Zabbix server is stored in a rational database and the application c This tutorial uses a **MariaDB** database with Zabbix. - Make sure to [initalize](/tutorials/mariadb-ubuntu-bionic/#securing-mariadb) your MariaDB server before configuring the database. + Make sure to [initialize](/tutorials/mariadb-ubuntu-bionic/#securing-mariadb) your MariaDB server before configuring the database. 1. Log into MariaDB with the user **root** and the password set during the installation. diff --git a/tutorials/zammad-ticketing/index.mdx b/tutorials/zammad-ticketing/index.mdx index 9142afecb6..616949fb97 100644 --- a/tutorials/zammad-ticketing/index.mdx +++ b/tutorials/zammad-ticketing/index.mdx @@ -31,7 +31,7 @@ Zammad is an open-source helpdesk system that allows you to oversee customer int This tutorial will guide you through the process of installing Zammad on a Scaleway Instance operating on **Ubuntu 20.04 LTS (Focal Fossa)**. Furthermore, you will receive a brief orientation of the application. - We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). If you are installing Zammad on Ubuntu 22.04 and up, avoid using an Instance with ARM architecure to follow this tutorial, as the package manager used upon installation is not compatible with the ARM architecture. + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). If you are installing Zammad on Ubuntu 22.04 and up, avoid using an Instance with ARM architecture to follow this tutorial, as the package manager used upon installation is not compatible with the ARM architecture.