docs: create Patching modules section; cleanup response wording

Signed-off-by: heitorlessa <[email protected]>

Author: heitorlessa

docs/content/core/tracer.mdx

@@ -58,7 +58,7 @@ You can trace your Lambda function handler via `capture_lambda_handler`.
 When using this decorator, Tracer performs these additional tasks to ease operations:
 
 * Creates a `ColdStart` annotation to easily filter traces that have had an initialization overhead
-* Adds any response, or full exceptions generated by the handler as metadata
+* Captures any response, or full exceptions generated by the handler, and include as tracing metadata
 
 ```python:title=lambda_handler.py
 from aws_lambda_powertools import Tracer
@@ -70,6 +70,8 @@ def handler(event, context):
     payment = collect_payment(charge_id)
     ...
 
+# Disables Tracer from capturing response and adding as metadata
+# Useful when dealing with sensitive data
 @tracer.capture_lambda_handler(capture_response=False) # highlight-line
 def handler(event, context):
 	return "sensitive_information"
@@ -170,7 +172,23 @@ def handler(evt, ctx): # highlight-line
     another_result = list(collect_payment_gen())
 ```
 
-## Tracing aiohttp requests
+## Patching modules
+
+Tracer automatically patches all [supported libraries by X-Ray](https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-python-patching.html) during initialization, by default. Underneath, AWS X-Ray SDK checks whether a supported library has been imported before patching.
+
+If you're looking to shave a few microseconds, or milliseconds depending on your function memory configuration, you can patch specific modules using `patch_modules` param:
+
+```python:title=app.py
+import boto3
+import requests
+
+from aws_lambda_powertools import Tracer
+
+modules_to_be_patched = ["boto3", "requests"]
+tracer = Tracer(patch_modules=modules_to_be_patched) # highlight-line
+```
+
+### Tracing aiohttp requests
 
 <Note type="info">
     This snippet assumes you have <strong>aiohttp</strong> as a dependency