fix(iam): review ro

Co-authored-by: Nathanael Demacon <[email protected]>
Co-authored-by: Rowena Jones <[email protected]>
Co-authored-by: Néda <[email protected]>

Author: 4 people

pages/iam/concepts.mdx

@@ -34,7 +34,7 @@ With the introduction of IAM, an API key is now associated with an IAM [user](#u
 
 ## Common Expression Language (CEL)
 
-Common Expression Language (CEL) is the expression language used to specify an expression in [conditions](#conditions) within an IAM policy. The language helps express attribute-based logic expressions. In general, a condition expression consists of one or more statements. Each statement expresses an attribute-based control rule, and ultimately determines whether the permissions applies. IAM conditions use the following CEL features: **Variables**, **Operators**, **Functions** and **Logical Operators**. Refer to the [Understanding policy conditions](/iam/reference-content/understanding-policy-conditions) documentation page for a detailed description of the supported CEL features.
+The Common Expression Language (CEL) is used to define expressions in [conditions](#conditions) within an IAM policy. CEL allows you to create attribute-based logic expressions that determine whether specific permissions apply. A condition expression typically consists of one or more statements, each defining an attribute-based control rule. IAM conditions use the following CEL features: **Variables**, **Operators**, **Functions**, and **Logical Operators**. Refer to the [Understanding policy conditions](/iam/reference-content/understanding-policy-conditions) documentation page for a detailed description of the supported CEL features.
 
 ## Conditions
 

pages/iam/how-to/create-policy.mdx

@@ -42,7 +42,7 @@ An IAM [policy](/iam/reference-content/policy/) is used to define the permission
 5. Click **Add rules** to progress to the next part of the policy creation wizard.
     <Lightbox src="scaleway-iam-create-policy-2.webp" alt="" />
     <Message type="tip">
-      Rules define the actions that the attached principal will be able to carry out within the Organization. When creating a rule, you first set the **scope** of the rule, and then select the **permission sets** to apply within the scope. You can optionally set up **contditions** for your rule. See our dedicated documentation for more help with [policies, rules, scopes and permission sets](/iam/reference-content/policy/).
+      Rules define the actions that the attached principal will be able to carry out within the Organization. When creating a rule, you first set the **scope** of the rule, and then select the **permission sets** to apply within the scope. You can optionally set up **conditions** for your rule. See our dedicated documentation for more help with [policies, rules, scopes and permission sets](/iam/reference-content/policy/).
     </Message>
 6. Select a **scope** for the rule:
     - To give the principal permissions to view, create, edit and/or delete [resources](/iam/concepts/#resource), select the **Access to resources** scope. Then, select the [Project](/iam/concepts/#project) in which you want the permissions to apply. You can select from **all current and future Projects**, **all current Projects** or select specific Projects.
@@ -55,7 +55,7 @@ An IAM [policy](/iam/reference-content/policy/) is used to define the permission
       Refer to the [Understanding policy conditions](/iam/reference-content/understanding-policy-conditions) documentation page for more details about how to write condition expressions, as well as examples of conditions.
     </Message>
 11. Click **Validate**. The rule, with its scope and permission sets, is added to the list of the policy's rules.
-12. Click **Add new rule** and repeat steps 6-8 as many times as required to add multiple rules to your policy.
+12. Click **Add new rule** and repeat steps 6 to 8 as many times as required to add multiple rules to your policy.
     <Message type="tip">
       You can delete <Icon name="delete" /> or edit <Icon name="edit" /> an existing rule by clicking the relevant button in the top right corner of the rule's summary.
     </Message>

pages/iam/quickstart.mdx

@@ -83,7 +83,7 @@ Users you have invited to your Organization, and applications you have created,
       Refer to the [Understanding policy conditions](/iam/reference-content/understanding-policy-conditions) documentation page for more details about how to write condition expressions, as well as examples of conditions.
     </Message>
 11. Click **Validate**. The rule, with its scope and permission sets, is added to the list of the policy's rules.
-12. Click **Add new rule** and repeat steps 6-8 as many times as required to add multiple rules to your policy.
+12. Click **Add new rule** and repeat steps 6 to 8 as many times as required to add multiple rules to your policy.
     <Message type="tip">
       You can delete <Icon name="delete" /> or edit <Icon name="edit" /> an existing rule by clicking the relevant button in the top right corner of the rule's summary.
     </Message>

pages/iam/reference-content/understanding-policy-conditions.mdx

@@ -33,7 +33,7 @@ Expressions at Scaleway are defined in CEL, which provides a human-readable and
 
 Common Expression Language is used to specify a IAM condition expression.
 
-Expressions consist of one or more statements that declare an attribute-based control rule, and determines whether a permission applies.
+Expressions consist of one or more statements that declare an attribute-based control rule, and determine whether a permission applies.
 
 IAM conditions use the following CEL features:
     - Variables
@@ -66,7 +66,7 @@ Refer to the official [CEL syntax specification](https://github.com/google/cel-s
 
 #### Logical operators
 
-Conditions supports three logical operators that can be used to build complex logic expressions from basic expression statements:
+Conditions support three logical operators that can be used to build complex logic expressions from basic expression statements:
 
 | Logical operator | Description | Example |
 | -- | ------------------- | ------ |
@@ -77,7 +77,7 @@ Conditions supports three logical operators that can be used to build complex lo
 
 ### Functions
 
-A function is a compound operator for data types that supports more complex operations. In condition expressions, there are predefined functions that can be used with a given data type.
+A function is a compound operator for data types, that supports more complex operations. In condition expressions, predefined functions can be used with a given data type.
 
 | Function | Description | Parameters |
 | ------------ | ------------------- | ------ |
@@ -96,7 +96,7 @@ For example, if you set up a policy that grants access to a resource only on Mon
 
 We recommend that you specify timezones when creating time-based conditions.
 
-Refer to the official [CEL specification](https://github.com/google/cel-spec/blob/master/doc/langdef.md#timezones) for the correct grammar to express timezones in conditions.
+Refer to the official [CEL specification](https://github.com/google/cel-spec/blob/master/doc/langdef.md#timezones) for the correct syntax to express timezones in conditions.
 
 ### Timestamps
 
@@ -121,7 +121,7 @@ request.user_agent.contains("terraform/")
 
 ### Time conditions
 
-To check if a request was performed at a specific timeslot you can use the following expression. In this example, use weekdays from 9am to 5pm as a timestamp.
+To check if a request was performed within a specific timeslot you can use the following expression. In this example, use weekdays from 9am to 5pm as a timestamp.
 ```
 request.time.getDayOfWeek() != 0 && request.time.getDayOfWeek() != 6
 && request.time.getHours("Europe/Paris") < 17