Fix highlight

Author: leandrodamascena

docs/core/event_handler/appsync.md

@@ -586,7 +586,7 @@ Here's an example of how you can test your synchronous resolvers:
 
 === "assert_graphql_response_module.py"
 
-    ```python hl_lines="11"
+    ```python hl_lines="10"
     --8<-- "examples/event_handler_graphql/src/assert_graphql_response_module.py"
     ```
 

docs/core/event_handler/bedrock_agents.md

@@ -319,7 +319,7 @@ Test your routes by passing an [Agent for Amazon Bedrock proxy event](https://do
 
 === "assert_bedrock_agent_response.py"
 
-	```python hl_lines="21-23 27"
+	```python hl_lines="22-24 28"
 	--8<-- "examples/event_handler_bedrock_agents/src/assert_bedrock_agent_response.py"
 	```
 

docs/core/metrics.md

@@ -425,7 +425,7 @@ You can read standard output and assert whether metrics have been flushed. Here'
 
     This will be needed when using `capture_cold_start_metric=True`, or when both `Metrics` and `single_metric` are used.
 
-    ```python hl_lines="20-21 27"
+    ```python hl_lines="21-22 28"
     --8<-- "examples/metrics/src/assert_multiple_emf_blobs.py"
     ```
 

docs/utilities/data_masking.md

@@ -671,7 +671,7 @@ Testing your code with a simple erase operation
 
 === "test_lambda_mask.py"
 
-```python hl_lines="22"
+```python
 --8<-- "examples/data_masking/tests/test_lambda_mask.py"
 ```