update other PPL page

Author: alexandreLamarre

content/docs/get-started/fundamentals/core/build-policies.md

@@ -115,7 +115,7 @@ There are four logical operators:
 
 In PPL, a criterion defines a specific condition to evaluate, such as a user’s email or device type.
 
-- Each criterion is an object where the key is the criterion name (optionally with a sub-path), and the value specifies what to match or compare.
+- Each criterion is an object where the key is the criterion name (optionally with a sub-path, delimited by `/`), and the value specifies what to match or compare.
 - The exact format of the value depends on the type of criterion being used.
 
 #### Matchers

content/docs/internals/ppl.mdx

@@ -53,11 +53,21 @@ It will deny access to users with a `[email protected]` **or** `[email protected]
 
 ## Rules
 
-A PPL document is either an object or an array of objects. The object represents a rule where the action is the key and the value is an object containing the logical operators.
+A rule is the basic building block of a PPL policy. Each rule says what action to take (allow or deny) and under what conditions.
+
+- The action (allow or deny) is the outcome if the conditions are met.
+- The conditions are expressed using logical operators, criteria, and matchers.
+
+A PPL document can contain:
+
+- A single rule, or
+- An array of rules (evaluated together).
 
 ## Actions
 
-Only two actions are supported: `allow` and `deny`. `deny` takes precedence over `allow`. More precisely: a user will have access to a route if **at least one** `allow` rule matches and **no** `deny` rules match.
+Actions are one of the two values : `allow` or `deny`. `deny` always takes precedence over `allow`.
+
+Users will have access to a route if **at least one** `allow` rule matches and **no** `deny` rules match.
 
 ## Logical Operators
 
@@ -123,7 +133,10 @@ Although these policies are equally effective, we recommend using just one opera
 
 ## Criteria
 
-Criteria in PPL are represented as an object where the key is the name and optional sub-path of the criterion, and the value changes depending on which criterion is used. A sub-path is indicated with a `/` in the name:
+In PPL, a criterion defines a specific condition to evaluate, such as a user’s email or device type.
+
+- Each criterion is an object where the key is the criterion name (optionally with a sub-path, delimited by `/`), and the value specifies what to match or compare.
+- The exact format of the value depends on the type of criterion being used.
 
 ```yaml
 allow: