run lint

Author: alexandreLamarre

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

@@ -64,14 +64,13 @@ PPL allows administrators to express authorization policy in a high-level, decla
 
 You can think of it as coded instructions to tell Pomerium how authorization decisions are made for capturing all niche and edge-case scenarios. It's as flexible as you want it to be!
 
-
-
 ### How does PPL work?
 
 PPL is made up of **Rules**, **Actions**, **Logical Operators**, **Criteria**, and **Matchers**.
 
 Below is a simple policy example in PPL format that allows access for the email [email protected]. The following sections will break down each of these components in more detail.
 
+<!-- prettier-ignore-start -->
 ```yaml
 # PPL Example
 policy:
@@ -81,6 +80,7 @@ policy:
       - email:                     # Criterion
           is: [email protected]   # Matcher
 ```
+<!-- prettier-ignore-end -->
 
 #### Rules
 
@@ -90,6 +90,7 @@ A rule is the basic building block of a PPL policy. Each rule says what action t
 - 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).
 
@@ -99,7 +100,6 @@ Actions are one of the two values : `allow` or `deny`. `deny` always takes prece
 
 Users will have access to a route if **at least one** `allow` rule matches and **no** `deny` rules match.
 
-
 #### Logical Operators
 
 A logical operator combines multiple criteria together for the evaluation of a rule.
@@ -114,7 +114,8 @@ There are four logical operators:
 #### Criteria
 
 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), 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/get-started/fundamentals/core/build-routes.md

@@ -59,7 +59,7 @@ routes:
             - email:
                 is: [email protected]
     pass_identity_headers: true
-# Add Grafana route here:
+  # Add Grafana route here:
   - from: https://grafana.localhost.pomerium.io
     to: http://grafana:3000
     allow_any_authenticated_user: true