fucking syntax highlighting

README.md

@@ -143,15 +143,15 @@ environment.evaluate(Variable.new("variable_a")) # => 2
 > [!CAUTION]
 > Ruby `symbols` are converted to `strings` when serialized to JSON, and remain `strings` when that JSON is parsed.
 >
-> ```ruby
-> environment = Environment.new(foo: "bar")
->
-> variable_foo = Variable.new(:foo)
-> environment.evaluate(variable_foo) #=> "bar"
->
-> variable_foo = PortableExpressions.from_json(variable_foo.to_json)
-> environment.evaluate(variable_foo) #=> MissingVariableError
-> ```
+```ruby
+environment = Environment.new(foo: "bar")
+
+variable_foo = Variable.new(:foo)
+environment.evaluate(variable_foo) #=> "bar"
+
+variable_foo = PortableExpressions.from_json(variable_foo.to_json)
+environment.evaluate(variable_foo) #=> MissingVariableError
+```
 
 ### Serialization (to JSON)
 
@@ -276,14 +276,14 @@ File.write("user_owns_resource_and_has_permission.json", user_owns_resource_and_
 
 > [!TIP]
 > These examples demonstrate portability via JSON files, but we can just as easily serve the policy directly to anyone who needs it via some HTTP controller:
->
-> ```ruby
-> # E.g. Rails via an `ActionController`
-> render json: user_owns_resource_and_has_permission.as_json, :ok
->
-> # Elsewhere, in the requesting service
-> user_owns_resource_and_has_permission = PortableExpressions.from_json(response.body.to_s)
-> ```
+
+```ruby
+# E.g. Rails via an `ActionController`
+render json: user_owns_resource_and_has_permission.as_json, :ok
+
+# Elsewhere, in the requesting service
+user_owns_resource_and_has_permission = PortableExpressions.from_json(response.body.to_s)
+```
 
 Then, some consumer with access to the user's permissions and context around the requested `resource` and `action` can execute the policy.