docs(SDB): update

Author: SamyOubouaziz

serverless/sql-databases/how-to/use-row-level-security.mdx

@@ -15,15 +15,15 @@ categories:
 
 Row-Level Security is a database security mechanism that allows access only to specific rows of a table based on a user's role or permissions.
 
-Row Level Security can be actived with Serverless SQL Database for a maximum 2 different roles having both read and write permissions. This can be used to restrict access to a subset of users with frameworks or tools such as [PostgREST](https://docs.postgrest.org/en/v12/).
+Row Level Security can be actived with Serverless SQL Databases for a maximum of two different roles, having both read and write permissions. This can be used to restrict access to a subset of users with frameworks or tools such as [PostgREST](https://docs.postgrest.org/en/v12/).
+
 This requires setting up different [IAM permissions sets](/identity-and-access-management/iam/reference-content/permission-sets/) for each role (**ServerlessSQLDatabaseFullAccess** or **ServerlessSQLDatabaseReadWrite** for one role, and **ServerlessSQLDatabaseDataReadWrite** for the other).
 
 <Macro id="requirements" />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 - [Created a Serverless SQL Database](/serverless/sql-databases/how-to/create-a-database/)
-- [Created two applications](/identity-and-access-management/iam/how-to/create-application/) in IAM
 
 ## Add sample data and create PostgreSQL Row Level Security
 
@@ -63,26 +63,24 @@ This requires setting up different [IAM permissions sets](/identity-and-access-m
 
 ## Create an IAM application with Row Level Security enabled
 
-1. Create a new [IAM application](/identity-and-access-management/iam/how-to/create-application/) or use an existing one.
+1. Create a new [IAM application](/identity-and-access-management/iam/how-to/create-application/).
 
 2. Create a new [IAM policy](/identity-and-access-management/iam/how-to/create-policy/), and add the **ServerlessSQLDatabaseDataReadWrite** permission set to the application you just created.
 
     <Message type="note">
-    You must provide **ServerlessSQLDatabaseDataReadWrite** permission set and not **ServerlessSQLDatabaseReadWrite** permission set. Indeed, all connections to your database performed with the former permissions set will use `role_readwrite` in PostgreSQL, whereas all connections performed with the latter or **ServerlessSQLDatabaseFullAccess** will use `role_admin` in PostgreSQL.
+    You must provide **ServerlessSQLDatabaseDataReadWrite** permission set and not **ServerlessSQLDatabaseReadWrite** permission set. Indeed, all connections to your database performed with the former permissions set will use `role_readwrite` in PostgreSQL, whereas all connections performed with the latter, or **ServerlessSQLDatabaseFullAccess** will use `role_admin` in PostgreSQL.
     </Message>
 
-3. Create an [API Key](/identity-and-access-management/iam/how-to/create-api-keys/) for this application and connect to your Serverless SQL Database with this application.
+3. Create an [API Key](/identity-and-access-management/iam/how-to/create-api-keys/) for this application, and connect to your Serverless SQL Database with this application.
     ```bash
     psql "postgres://[new-application-id]:[new-api-secret-key]@[database-hostname]:5432/[database-name]?sslmode=require"
     ```
 
-4. Run the follwoing command to list the `pets` this application has access to with:
+4. Run the following command to list the `pets` this application has access to:
     ```sql
     SELECT * FROM pets;
     ```
-    Only the pets with a `keeper` column value of `role_readwrite`.
-
-    Your new application can now only access a specific subset of rows based on its permissions.
+    Only the pets with a `keeper` column value of `role_readwrite` display. Your new application can now only access a specific subset of rows based on its permissions.
 
     <Message type="tip">
     Row level security and policies can be created or deleted by a table owner. In this example, you can check table owner with the following command: