scaleway · SamyOubouaziz · Nov 14, 2024 · Nov 14, 2024 · Nov 14, 2024
diff --git a/...eptember2024/2024-09-19-containers-changed-containers-vcpu-and-ram-relation.mdx b/...eptember2024/2024-09-19-containers-changed-containers-vcpu-and-ram-relation.mdx
@@ -1,5 +1,5 @@
 ---
-title: Relationship between VCPU and RAM rationalized
+title: Relationship between vCPU and RAM rationalized
 status: changed
 author:
     fullname: 'Join the #serverless-containers channel on Slack.'
@@ -9,5 +9,5 @@ category: serverless
 product: containers
 ---
 
-Serverless Containers now imposes constraints on RAM based on the selected VCPU. This is in order to promote coherent usage of memory and power.
+Serverless Containers now imposes constraints on RAM based on the selected vCPU. This is in order to promote coherent usage of memory and power.
 
diff --git a/changelog/serverless/october2022/2022-10-13-containers-added-memory-cpu.mdx b/changelog/serverless/october2022/2022-10-13-containers-added-memory-cpu.mdx
@@ -9,4 +9,4 @@ category: serverless
 product: containers
 ---
 
-New tiers for Serverless Containers (3GB/1680 mVCPU & 4GB/2240 mVCPU) available.
+New tiers for Serverless Containers (3GB/1680 mvCPU & 4GB/2240 mvCPU) available.
diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx
@@ -56,7 +56,7 @@ Serverless Containers are billed on a pay-as-you-go basis, strictly on resource
 |--------------------------- |--------------	|
 | Monthly duration           | 30 000 000 s 	|
 | Amount of memory allocated | 128 MB       	|
-| Amount of vCPU allocated   | 70 mVCPU     	|
+| Amount of vCPU allocated   | 70 mvCPU     	|
 | Free tier                  | Yes          	|
 
 #### Price calculation
@@ -68,7 +68,7 @@ Serverless Containers are billed on a pay-as-you-go basis, strictly on resource
     * *Billed resources:* 3 750 000 - 400 000 = 3 350 000 GB-s
     * *Cost:* 3 350 000 * €0.0000010 = **€3.35**
 * **vCPU consumption**
-    * *Allocated vCPU conversion:* 70mVCPU = 0.070 vCPU
+    * *Allocated vCPU conversion:* 70mvCPU = 0.070 vCPU
     * *Resource consumption:* 30 000 000 s * 0.070 vCPU = 2 100 000 vCPU-s
     * *Free tier:* 200 000 vCPU-s
     * *Billed resources:* 2 100 000 - 200 000 = 1 900 000 vCPU-s

diff --git a/faq/serverless-jobs.mdx b/faq/serverless-jobs.mdx
@@ -54,7 +54,7 @@ Serverless Jobs are billed on a pay-as-you-go basis, strictly on resource consum
 |--------------------------- |------------------|
 | Monthly duration           | 432 000 s (120h) |
 | Amount of memory allocated | 2048 MB          |
-| Amount of vCPU allocated   | 1120 mVCPU       |
+| Amount of vCPU allocated   | 1120 mvCPU       |
 | Free tier                  | Yes              |
 
 #### Price calculation
@@ -66,7 +66,7 @@ Serverless Jobs are billed on a pay-as-you-go basis, strictly on resource consum
     * *Billed resources:* 864 000 - 400 000 = 464 000 GB-s
     * *Cost:* 464 000 * €0.0000010 = **€0.47**
 * **vCPU consumption**
-    * *Allocated vCPU conversion:* 1120 mVCPU = 1.12 vCPU
+    * *Allocated vCPU conversion:* 1120 mvCPU = 1.12 vCPU
     * *Resource consumption:* 432 000 s * 1.12 vCPU =  483 840 vCPU-s
     * *Free tier:* 200 000 vCPU-s
     * *Billed resources:* 483 840 - 200 000 = 283 840 vCPU-s

diff --git a/serverless/containers/concepts.mdx b/serverless/containers/concepts.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Key concepts of Scaleway Serverless Containers.
 tags: containers cold-start concurrency container-registry gbs environment-variables jwt vcpu
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-14
 categories:
   - serverless
 ---
@@ -19,7 +19,7 @@ Cold start is the time a Container takes to handle a request when it is called f
 Startup process steps are:
 * Downloading the container image to our infrastructure
 * Starting the container. Optimize your container startup speed to minimize this step (e.g., avoid waiting for slow connections or downloading large objects at startup)
-* Waiting for the containeer to listen on the configured port.
+* Waiting for the container to listen on the configured port.
 
 [How to reduce cold starts](/faq/serverless-containers/#how-can-i-reduce-the-cold-starts-of-serverless-containers)
 
@@ -29,7 +29,7 @@ Concurrency defines the number of simultaneous requests a single instance of you
 
 ## Container
 
-A container is a package of software that includes all dependencies: code, runtime, configuration, and system libraries so that it can run on any host system. Scaleway provides custom Docker images that are entirely handled for you in the cloud. With Containers, you can rely on your favorite technologies such as Django or Ruby on Rails.
+A container is a package of software that includes all dependencies: code, runtime, configuration, and system libraries so that it can run on any host system. Scaleway provides custom Docker images that are entirely handled for you in the cloud. With Containers, you can rely on your favorite technologies such as Django, or Ruby on Rails.
 
 ## Container Registry
 
@@ -41,11 +41,11 @@ A CRON trigger is a mechanism used to automatically invoke a Serverless Function
 
 ## Environment variables
 
-An environment variable is a variable whose value is set outside the program, typically through functionality built into the operating system or microservice. An environment variable is made up of a name/value pair, and any number may be created and available for reference at a point in time.
+An environment variable is a variable whose value is set outside the program, typically through functionality built into the operating system, or microservice. An environment variable is made up of a name/value pair, and any number may be created and available for reference at a point in time.
 
 ## Ephemeral storage
 
-In addition to VCPU and RAM, Serverless Containers also provide a storage volume for the duration of the task. This storage space allows to hold the data retrieved by the job, and disappears once the execution is complete. The maximum size of the ephemeral storage is tied to the allocated memory.
+In addition to vCPU and RAM, Serverless Containers also provide a storage volume for the duration of the task. This storage space allows to hold the data retrieved by the job, and disappears once the execution is complete. The maximum size of the ephemeral storage is tied to the allocated memory.
 
 ## GB-s
 
@@ -59,9 +59,9 @@ An image is a blueprint from which an arbitrary number of brand-new containers c
 
 JWT (JSON Web Token) is an access token you can create from the console or API to enable an application to access your Private Container. Consult the [Developer documentation](https://www.scaleway.com/en/developers/api/serverless-containers/#path-tokens) for more details.
 
-## mVCPU
+## mvCPU
 
-A vCPU (Virtual Central Processing Unit) is equivalent to 1000 mVCPU.
+A [vCPU](#vcpu) (Virtual Central Processing Unit) is equivalent to 1000 mvCPU.
 
 ## Namespace
 

diff --git a/serverless/functions/concepts.mdx b/serverless/functions/concepts.mdx
@@ -5,16 +5,16 @@ meta:
 content:
   h1: Functions - Concepts
   paragraph: Learn the core concepts and principles behind Scaleway's Serverless Functions.
-tags: functions cold-start environment-variables gbs jwt handler serverless
+tags: functions cold-start environment-variables gbs jwt handler serverless concept definition
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-14
 categories:
   - serverless
 ---
 
 ## Cold Start
 
-Cold Start is the time a Fuction takes to handle a request when it is called for the first time.
+Cold Start is the time a function takes to handle a request when it is called for the first time.
 
 Startup process steps are:
 * Downloading the container image (which contains the built Function) to our infrastructure
@@ -68,13 +68,13 @@ The runtime is the execution environment of your function. Regarding Serverless
 
 ## Sandbox
 
-A sandbox is an isolation area for your container. Serverless Containers offer two sandboxing environments:
+A sandbox is an isolation area for your function. Serverless Functions offer two sandboxing environments:
 - **v2** - Recommended for faster cold starts.
 - **v1** - Legacy sandboxing with slower cold start, but fully supports Linux system call interface.
 
 ## Scale to zero
 
-One of the advantages of Serverless Function is that when your function is not triggered, it does not consume any resources, which allows great savings.
+One of the advantages of Serverless Functions is that when your function is not triggered, it does not consume any resources, which allows for significant savings.
 
 ## Scaling
 

diff --git a/serverless/jobs/concepts.mdx b/serverless/jobs/concepts.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Key concepts of Scaleway Serverless Jobs.
 tags: jobs serverless-jobs definition glossary execution run
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-14
 categories:
   - serverless
 ---

diff --git a/serverless/jobs/how-to/monitor-job.mdx b/serverless/jobs/how-to/monitor-job.mdx
@@ -36,7 +36,7 @@ Make sure that you have created a Grafana user and [retrieved their username and
 2. Click the name of the job you want to monitor. The **Overview** tab displays: 
     - The **Job definition** section contains the parameters of your Serverless job, and provides the following elements:
       - Region
-      - Provisioned mVCPU and memory
+      - Provisioned mvCPU and memory
       - Provisioned ephemeral storage
       - Container image used
       - Cron schedule 

diff --git a/serverless/jobs/reference-content/jobs-limitations.mdx b/serverless/jobs/reference-content/jobs-limitations.mdx
@@ -23,7 +23,7 @@ This section contains usage limits that apply when using Serverless Jobs.
 | Number of job definitions max | 1000       | Organization |
 | Max parallel jobs             | 400        | Organization |
 | Max ephemeral storage         | 10 GB      | Job run      |
-| CPU max                       | 6 VCPU     | Job run      |
+| CPU max                       | 6 vCPU     | Job run      |
 | Memory max                    | 16 GB      | Job run      |
 | Timeout                       | 24h        | Job run      |
 

diff --git a/serverless/sql-databases/concepts.mdx b/serverless/sql-databases/concepts.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Detailed explanation of concepts and architecture behind Scaleway's serverless SQL databases.
 tags: sql databases serverless
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-14
 categories:
   - serverless
 ---
@@ -22,7 +22,7 @@ Autoscaling can automatically scale your database resources up or down, dependin
 
 ## Backup
 
-A database backup is a copy of the data stored in the database (including data structure, such as tables). Database backups in Serverless SQL Databases are logical backups (as opposed to raw disk volume backups, also called "snapshots"). Database backups can be restored in the current database or any other PostgreSQL database and, allow recovery from database crashes, data corruption, or data loss.
+A database backup is a copy of the data stored in the database (including data structure, such as tables). Database backups in Serverless SQL Databases are logical backups (as opposed to raw disk volume backups, also called "snapshots"). Database backups can be restored in the current database or any other PostgreSQL database, and allow recovery from database crashes, data corruption, or data loss.
 
 ## Cold start
 
@@ -34,7 +34,7 @@ Connection pooling is the process of mutualizing client connections used to conn
 
 ## Credentials
 
-Credentials are the login and password (also called "username" and "password" in PostgreSQL vocabulary) used by a user or an application to connect to a database. With Scaleway Serverless SQL Databases, logins are [IAM principal IDs](/identity-and-access-management/iam/concepts/#principal) and passwords are [IAM secret keys](/identity-and-access-management/iam/concepts/#api-key).
+Credentials are the login and password (also called "username" and "password" in PostgreSQL vocabulary) used by a user, or an application to connect to a database. With Scaleway Serverless SQL Databases, logins are [IAM principal IDs](/identity-and-access-management/iam/concepts/#principal) and passwords are [IAM secret keys](/identity-and-access-management/iam/concepts/#api-key).
 
 ## Database engine
 

diff --git a/styles/Vocab/Scaleway/accept.txt b/styles/Vocab/Scaleway/accept.txt
@@ -44,7 +44,7 @@ KubeConfig
 MiniKube
 ReplicaSet
 Docker
-mVCPU
+mvCPU
 JWT
 vCPU
 ACL

diff --git a/tutorials/deploy-umami-on-serverless-containers/index.mdx b/tutorials/deploy-umami-on-serverless-containers/index.mdx
@@ -73,7 +73,7 @@ Umami is a simple, easy-to-use, self-hosted web analytics solution. It provides
 2. Click **+ Deploy a Container**. The container deployment wizard displays.
 3. Choose the namespace you pushed the image to and select the `umami:postgresql-latest` image. Set the value for the port to `3000`.
 4. Enter a name for your container. Optionally, you can enter a container description.
-5. Select the resources you want to allocate to the container. The resources to allocate depend on the intended load of your application. In this tutorial we use **128 MB - 70 mVCPU**.
+5. Select the resources you want to allocate to the container. The resources to allocate depend on the intended load of your application. In this tutorial we use **128 MB - 70 mvCPU**.
 6. Configure the minimum and maximum values to autoscale the number of available instances for your container.
 7. Set the Secrets. Secrets are an extra-secure type of environment variables that are injected into your container and stored securely:
     <Lightbox src="scaleway-serverless-secrets.webp" alt="" />

diff --git a/tutorials/transform-bucket-images-triggers-functions-deploy/index.mdx b/tutorials/transform-bucket-images-triggers-functions-deploy/index.mdx
@@ -324,7 +324,7 @@ You will now learn how to deploy Serverless Functions and connect them using tri
 3. Select **NodeJS 20**.
 4. Select **Upload a ZIP** and upload the **BucketScan.zip** archive previously created.
 5. Name the function **bucketscan**.
-6. Set **resources** to 1024 MB - 560 mVCPU.
+6. Set **resources** to 1024 MB - 560 mvCPU.
 7. Enter the following **environment variables**:
     - `SQS_ENDPOINT`: the endpoint of Messaging and Queuing SQS (which you previously activated).
     - `QUEUE_URL`: the URL of the Queue previously created.
@@ -363,7 +363,7 @@ You will now learn how to deploy Serverless Functions and connect them using tri
 3. Select **NodeJS 20**.
 4. Select **Upload a ZIP** and upload the **ImageTransform.zip** archive previously created.
 5. Name the function **imagetransform**.
-6. Set **resources** to 1024 MB - 560 mVCPU.
+6. Set **resources** to 1024 MB - 560 mvCPU.
 7. Enter the following **environment variables**:
     - `RESIZED_WIDTH`: the width (in pixels) you want to resize your images to.
     - `DESTINATION_BUCKET`: the name of your destination bucket (e.g.: `dest-images-<YOUR_NAME>`).
-Original file line number
+Diff line change
@@ Expand Up / @@ -44,7 +44,7 @@ KubeConfig @@
     MiniKube
     ReplicaSet
     Docker
-    mVCPU
+    mvCPU
     JWT
     vCPU
     ACL
@@ Expand Down @@