Error PR - do not merge

faq/serverless-functions.mdx

@@ -6,7 +6,7 @@ content:
   h1: Serverless Functions
 hero: assets/faas.webp
 dates:
-  validation: 2024-03-25
+  validation: 2024-10-03
 category: serverless
 ---
 
@@ -16,21 +16,21 @@ category: serverless
 
 Serverless Functions is billed on a pay-as-you-go basis. Three components are taken into account:
 
-* **Monthly Request number:** each time your function is invoked we increase a counter.
+* **Monthly request number:** each time your function is invoked we increase a counter.
 
 * **Resource consumption:** this component is obtained by multiplying the memory tiers chosen by the duration of each function invocation.
 
-* **Resources provision:** in order to mitigate cold start, users can choose to keep some function Instances warm (by filing the min scale value). We then charge for the provisioned resources similarly to the Resources consumption component.
+* **Resources provision:** in order to mitigate cold start, users can choose to keep some function instances warm (by filing the minimum scale value). We then charge for the provisioned resources similarly to the Resources consumption component.
 
 The scheme below illustrates our billing model:
 
 <Lightbox src={["scaleway-Billing-FaaS-1-DEF.webp", "scaleway-Billing-FaaS-2-DEF.webp"]} size={"medium"}  alt={["Functions Billing", "Functions Billing"]} />
 
 ### Pricing
 
-* **Monthly requests:** **€0.15 per million requests** and we offer **1M free requests** per account per month.
+* **Monthly requests:** **€0.15 per million requests**, and we offer **1M free requests** per account per month.
 
-* **Resources consumption:**  **€1.20 per 100 000 GB-s** and we provide **400 000 GB-s free tiers** per account and per month.
+* **Resources consumption:** **€1.20 per 100 000 GB-s**, and we provide **400 000 GB-s free tiers** per account and per month.
 
 | Memory provisioned  | Cost per second |
 |---------------------|-----------------|
@@ -157,7 +157,7 @@ Serverless Functions use cases are wide so [several ways to deploy functions](/s
 
 ## How can I test my functions locally?
 
-Local development is useful for debugging, profiling, testing etc... so we provide libraries to do this: [local testing doc](/serverless/functions/reference-content/local-testing/).
+ Scaleway provide libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless/functions/reference-content/local-testing/) for more information.
 
 ## Where can I find some advanced code examples for functions?
 
@@ -166,4 +166,4 @@ Check out our [serverless-examples repository](https://github.com/scaleway/serve
 ## How to migrate runtimes?
 
 There are no constraints when changing a function runtime, you simply need to choose the runtime version you want.
-Upgrading a runtime is highly recommended in case of deprecation, and for runtimes that have reached end-of-support or end-of-life. See the [functions runtimes lifecycle documentation](/serverless/functions/reference-content/functions-lifecycle/) for more information.
+Upgrading a runtime is highly recommended in case of deprecation, and for runtimes that have reached end-of-support or end-of-life. Refer to the [functions runtimes lifecycle documentation](/serverless/functions/reference-content/functions-lifecycle/) for more information.

faq/serverless-jobs.mdx

@@ -6,7 +6,7 @@ content:
   h1: Serverless Jobs
 hero: assets/serverless-jobs.webp
 dates:
-  validation: 2024-03-25
+  validation: 2024-10-03
 category: serverless
 ---
 
@@ -83,12 +83,12 @@ Serverless Jobs are integrated with [Cockpit](/observability/cockpit/quickstart/
 
 ## Can I cancel or modify a Serverless Job after it has started?
 
-An ongoing Serverless Job can be interrupted during its execution from the **Job runs** section of a job's **Overview** tab.
+An ongoing Serverless Job can be interrupted during its execution from the **Job runs** section of a job's **Overview** tab. Refer to the [dedicated docmentation](/serverless/jobs/how-to/stop-job/) for more information.
 
 ## How can I automate the deployment and management of Scaleway Serverless Jobs?
 
 Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be driven using the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/), the [Scaleway API](https://www.scaleway.com/en/developers/api/), and other [developer tools](https://www.scaleway.com/en/developers/). Our serverless ecosystem offers a lot of possibilities with event-driven architectures, and integrations with more products of the Scaleway ecosystem are under active development.
 
-## Do Serverless Jobs offer parallelization?
+## Can I run multiple Serverless Jobs at the same time?
 
-Not yet. Scaleway Serverless Jobs will soon offer parallelization via a `parallelism` parameter for each job. This will automatically launch a given number of replicas of the Job container in parallel.
+When starting a Job, you can use contextual options to define the number of jobs to execute at the same time. Refer to the [dedicated documentation](/serverless/jobs/how-to/run-job/#how-to-run-a-job-with-contextual-options) for more information.

faq/serverless-sql-databases.mdx

@@ -14,7 +14,7 @@ category: serverless
 
 You are billed both for the compute resources provisioned and the storage used. You can see the cost estimate in the Database creation wizard.
 
-  - **Compute**: You are billed based on compute resources (vCPU and RAM) provisioned to handle your workload. Provisioned resources evolve according to the [autoscaling](/serverless/sql-databases/reference-content/serverless-sql-databases-overview/#autoscaling) parameter and stay between the minimum and maximum thresholds defined for your database. For each vCPU provisioned, 4 GB of RAM will be allocated.
+  - **Compute**: You are billed based on compute resources (vCPU and RAM) provisioned to handle your workload. Provisioned resources evolve according to the [autoscaling](/serverless/sql-databases/reference-content/serverless-sql-databases-overview/#autoscaling) parameter, and stay between the minimum and maximum thresholds defined for your database. For each vCPU provisioned, 4 GB of RAM will be allocated.
 
   - **Storage**: You are billed for the storage consumed by your database. Storage price is based on the size of your database (in GB) and includes 7 days of automated backups at no additional costs. Storage is always billed even if your database is in an active state or idle state.
 

menu/navigation.json

@@ -3949,12 +3949,16 @@
                     "label": "Manage user permissions for Serverless SQL Databases",
                     "slug": "manage-permissions"
                   },
+                  {
+                    "label": "Use Row-Level Security on a database",
+                    "slug": "use-row-level-security"
+                  },
                   {
                     "label": "Edit a Serverless SQL Database's autoscaling",
                     "slug": "configure-autoscaling"
                   },
                   {
-                    "label": "How to manage backups for Serverless SQL Databases",
+                    "label": "Manage backups for Serverless SQL Databases",
                     "slug": "manage-backups"
                   },
                   {
@@ -3978,6 +3982,10 @@
                   {
                     "label": "Securing connections using SSL/TLS",
                     "slug": "secure-connection-ssl-tls"
+                  },
+                  {
+                    "label": "Using Row-Level Security with PostgREST",
+                    "slug": "postgrest-row-level-security"
                   }
                 ],
                 "label": "API/CLI",
@@ -5333,4 +5341,4 @@
     ],
     "label": "Additional Services"
   }
-]
+]

serverless/containers/how-to/add-a-custom-domain-to-a-container.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Add a custom domain to Scaleway Serverless Containers.
 tags: custom-domain container serverless cname record
 dates:
-  validation: 2024-03-27
+  validation: 2024-10-03
   posted: 2022-02-21
 categories:
   - serverless
@@ -81,15 +81,15 @@ HTTP-01 challenge failure (and by extension, a custom domain in `error` status)
 | DNS record is not available yet. | This can be the case if the custom domain is created immediately after the CNAME is configured on your DNS provider side. | As a rule of thumb, wait a few minutes after creating the CNAME on your DNS provider, or at least wait until the DNS record is available on main resolvers (`1.1.1.1`, `8.8.8.8`). |
 | DNS cache is stale (still pointing to an old endpoint). | If the custom domain was pointing to another endpoint before adding the CNAME record to the Serverless Container, and if the TTL is greater than the maximum time of the check (3 min), it can sometimes happen that the custom domain still resolves to the old endpoint, thus making the challenge fail. | Wait until DNS entry is available and use a smaller TTL. |
 | Negative DNS cache is stale | If the initial check fails (DNS record is not available yet), and the negative TTL configured on your DNS provider side is high, the negative TTL will prevent subsequent checks from querying the nameserver again, until it expires. Depending on the negative TTL configured, this can take more or less time. | Either reduce the negative TTL in your DNS provider configuration, or just wait until you are sure DNS record is available. If you already tried to add the custom domain and faced this issue, you likely have to wait for the negative TTL to expire before making another attempt (so the cache can also expire on our side). |
-| Route `/.well-known/acme-challenge` is not handled correctly. | To perform the HTTP-01 challenge, a call will be made on `<your_custom_domain>/.well-known/acme-challenge/<token>`. If you are using a proxying/caching tool (like Cloudflare) between the custom domain and the Serverless Container endpoint, a cached version of that route can be served, making the check fails. | Don't configure caching rules for routes starting with `/.well-known/acme-challenge`. See an example below with Cloudflare. |
+| Route `/.well-known/acme-challenge` is not handled correctly. | To perform the HTTP-01 challenge, a call will be made on `<your_custom_domain>/.well-known/acme-challenge/<token>`. If you are using a proxying/caching tool (like Cloudflare) between the custom domain and the Serverless Container endpoint, a cached version of that route can be served, making the check fails. | Do not configure caching rules for routes starting with `/.well-known/acme-challenge`. Rerfer to the example below with Cloudflare. |
 
 Example of configuration on Cloudflare to disable caching with "Cache rules":
 
 <Lightbox src="cloudflare-bypass-cache-well-known-acme-challenge.webp" size="medium" alt="Bypass cache for /.well-known/acme-challenge routes" />
 
 ## Migrating an active domain
 
-Read this section if you are trying to migrate a domain that is already serving a live website/API/web application -- but not yet hosted on a Serverless Container -- and you are trying to migrate.
+Read this section if you are trying to migrate a domain that is already serving a live website/API/web application, but not yet hosted on a Serverless Container.
 
 To clarify, let's take a concrete example:
 

serverless/containers/reference-content/containers-concurrency.mdx

@@ -6,7 +6,7 @@ content:
   h1: Containers concurrency
   paragraph: Learn about concurrency settings for Scaleway Serverless Containers.
 dates:
-  validation: 2024-03-26
+  validation: 2024-10-03
   posted: 2024-03-26
 tags: serverless containers concurrency concurrent execution scaling parallelism parallel instances
 categories:
@@ -20,8 +20,6 @@ Concurrency determines the number of incoming requests a single instance of a co
 
 A higher number of instances processing requests at the same time implies a greater usage of memory and [vCPU](/serverless/containers/concepts/#vcpu), and consequently a higher cost.
 
-
-
 ## Maximum concurrent requests per instance
 
 When [deploying a container](/serverless/containers/how-to/deploy-a-container-from-scaleway-container-registry/), Scaleway Serverless Containers allows you to edit the **Maximum concurrent requests per instance** parameter.

serverless/containers/reference-content/deploy-container.mdx

@@ -6,7 +6,7 @@ content:
   h1: Methods to deploy Serverless Containers
   paragraph: Step-by-step guide to deploying a container on Scaleway.
 dates:
-  validation: 2024-03-27
+  validation: 2024-10-03
   posted: 2023-03-10
 ---
 
@@ -58,7 +58,7 @@ Installation instructions and documentation are available in the [Scaleway CLI r
 
 ## Scaleway SDKs
 
-The Scaleway SDKs allow you to manage your resources directly from your favorite languages.
+The Scaleway Software Development Kits (SDK) allow you to manage your resources directly from your favorite languages.
 
 The available SDKs are:
 

serverless/functions/reference-content/local-testing.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to test your Serverless Functions locally before deployment on Scaleway.
 tags: functions serverless local testing
 dates:
-  validation: 2024-03-27
+  validation: 2024-10-03
   posted: 2023-03-06
 categories:
   - serverless
@@ -51,5 +51,5 @@ with different libraries available to your local development environment.
 Performance during local testing can differ from the deployed Serverless Functions environment, and will involve [limitations](/serverless/functions/reference-content/functions-limitations/) around resource usage and quotas.
 
 <Message type="note">
-CPU/Memory settings do not apply when testing functions locally.
+CPU/memory settings do not apply when testing functions locally.
 </Message>

serverless/jobs/reference-content/jobs-limitations.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Learn the limitations of Scaleway Serverless Jobs.
 tags: Jobs limitations serverless
 dates:
-  validation: 2024-03-28
+  validation: 2024-10-03
   posted: 2021-03-28
 categories:
   - serverless
@@ -25,7 +25,7 @@ This section contains usage limits that apply when using Serverless Jobs.
 | Max ephemeral storage         | 10 GB      | Job run      |
 | CPU max                       | 6 VCPU     | Job run      |
 | Memory max                    | 16 GB      | Job run      |
-| timeout                       | 24h        | Job run      |
+| Timeout                       | 24h        | Job run      |
 
 ## Default values for CPU and memory limits
 
@@ -40,9 +40,9 @@ When the job vCPU and/or memory are not provided by the client, these default va
 
 Scaleway Serverless Jobs only supports `amd64` architecture for images.
 
-For example, if you build an image using an ARM CPU, such as Apple Silicon, your image will be in the `arm64` architecture, and you will have an error message during deployment.
+For example, if you build an image using an ARM CPU, such as Apple Silicon, your image will be using the `arm64` architecture, and you will have an error message during deployment.
 
-You must ensure that you build your image to target `amd64` architecture.
+You must ensure that you build your image to target the `amd64` architecture.
 
 ## Ports restrictions
 

serverless/jobs/troubleshooting/common-errors.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Troubleshoot common errors in Scaleway Serverless Jobs.
 tags: serverless jobs troubleshooting issue error message
 dates:
-  validation: 2024-03-28
+validation: 2024-10-03
   posted: 2024-03-28
 categories:
   - serveless