Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

Author: SamyOubouaziz

menu/navigation.json

@@ -3950,7 +3950,7 @@
                     "slug": "manage-permissions"
                   },
                   {
-                    "label": "Use Row Level Security on a database",
+                    "label": "Use Row-Level Security on a database",
                     "slug": "use-row-level-security"
                   },
                   {
@@ -3984,7 +3984,7 @@
                     "slug": "secure-connection-ssl-tls"
                   },
                   {
-                    "label": "Using Row Level Security with PostgREST",
+                    "label": "Using Row-Level Security with PostgREST",
                     "slug": "postgrest-row-level-security"
                   }
                 ],

serverless/sql-databases/api-cli/postgrest-row-level-security.mdx

@@ -1,10 +1,10 @@
 ---
 meta:
-  title: How to use Row Level Security with PostgREST for Serverless SQL Databases
-  description: This page provides the steps to use Row Level Security with PostGREST for Serverless SQL Databases
+  title: How to use Row-Level Security with PostgREST for Serverless SQL Databases
+  description: This page provides the steps to use Row-Level Security with PostGREST for Serverless SQL Databases
 content:
-  h1: How to use Row Level Security with PostgREST for Serverless SQL Databases
-  paragraph: This page provides the steps to use Row Level Security with PostGREST for Serverless SQL Databases
+  h1: How to use Row-Level Security with PostgREST for Serverless SQL Databases
+  paragraph: This page provides the steps to use Row-Level Security with PostGREST for Serverless SQL Databases
 tags: sql-databases serverless database row-level-security postgresql postgrest
 dates:
   validation: 2024-09-24
@@ -17,6 +17,8 @@ PostgREST's built-in Row Level Security based on users JWT relies either on [rol
 
 Due to connection pooling, Serverless SQL Databases currently only support transaction-scoped settings and requires using a single PostgreSQL role for all queries (the internal `role_readwrite` in PostgreSQL).
 
+<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/)

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

@@ -1,10 +1,10 @@
 ---
 meta:
-  title: How to use Row Level Security with Serverless SQL Database
-  description: This page explains how to use Row Level Security with Serverless SQL Databases
+  title: How to use Row-Level Security with Serverless SQL Database
+  description: This page explains how to use Row-Level Security with Serverless SQL Databases
 content:
-  h1: How to use Row Level Security with Serverless SQL Database
-  paragraph: This page explains how to use Row Level Security with Serverless SQL Databases
+  h1: How to use Row-Level Security with Serverless SQL Database
+  paragraph: This page explains how to use Row-Level Security with Serverless SQL Databases
 tags: sql-databases serverless database row-level-security postgresql postgrest
 dates:
   validation: 2024-09-24
@@ -15,7 +15,7 @@ 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 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/).
+Row-Level Security can be activated 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).
 
@@ -38,7 +38,7 @@ This requires setting up different [IAM permissions sets](/identity-and-access-m
     INSERT INTO pets VALUES ('Stuart','role_admin',1),('Nemo','role_admin',2),('Alfie','role_readwrite',3),('Peanut','role_readwrite',4);
     ```
 
-3. Run the command below to enable **Row Level Security**:
+3. Run the command below to enable **Row-Level Security**:
     ```sql
     ALTER TABLE pets ENABLE row level security;
     ```
@@ -55,7 +55,7 @@ This requires setting up different [IAM permissions sets](/identity-and-access-m
     All the data contained in the database displays, as you are connected with `role_admin`.
 
     <Message type="tip">
-    You can verify the current role your are connected with using the following command:
+    You can verify the current role you are connected with using the following command:
     ```sql
     SELECT current_user;
     ```
@@ -83,7 +83,7 @@ This requires setting up different [IAM permissions sets](/identity-and-access-m
     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:
+    Row-level security and policies can be created or deleted by a table owner. In this example, you can check the table owner with the following command:
     ```sql
     select * from pg_tables where tablename = 'pets';
     ```