docs(SDB): update

Author: SamyOubouaziz

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

@@ -48,7 +48,7 @@ This requires setting up different [IAM permissions sets](/identity-and-access-m
     CREATE POLICY pets_keeper ON pets TO role_readwrite USING (keeper = current_user);
     ```
 
-5. (Optional) Check that you can see all the data with your current connection:
+5. (Optional) Run the command below to check that you can see all the data with your current connection:
     ```sql
     SELECT * FROM pets;
     ```
@@ -63,27 +63,30 @@ 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](https://www.scaleway.com/en/docs/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/) or use an existing one.
 
-2. Add **ServerlessSQLDatabaseDataReadWrite** permission set to this application by creating a new [IAM policy](https://www.scaleway.com/en/docs/identity-and-access-management/iam/how-to/create-policy/)
+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="tip">
-    You need to provide **ServerlessSQLDatabaseDataReadWrite** permission set and not **ServerlessSQLDatabaseReadWrite** permission set. Indeed, all connections to your database performed with **ServerlessSQLDatabaseDataReadWrite** permissions will use `role_readwrite` in PostgreSQL, whereas all connections performed with **ServerlessSQLDatabaseReadWrite** or **ServerlessSQLDatabaseFullAccess** will use `role_admin` in PostgreSQL.
+    <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.
     </Message>
 
-3. Create an [API Key](https://www.scaleway.com/en/docs/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. List the `pets` this application has access to with:
+4. Run the follwoing command to list the `pets` this application has access to with:
     ```sql
     SELECT * FROM pets;
     ```
-    You should only see pets with a `keeper` column value of `role_readwrite`.
+    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.
 
     <Message type="tip">
-    Note that 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 `select * from pg_tables where tablename = 'pets';`.
+    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:
+    ```sql
+    select * from pg_tables where tablename = 'pets';
+    ```
     </Message>