docs: Correct internal links to tracer

Author: Michael Brewer

docs/utilities/middleware_factory.md

@@ -60,7 +60,7 @@ You can also have your own keyword arguments after the mandatory arguments.
 
 ## Tracing middleware execution
 
-If you are making use of [Tracer](/core/tracer), you can trace the execution of your middleware to ease operations.
+If you are making use of [Tracer](../core/tracer.md), you can trace the execution of your middleware to ease operations.
 
 This makes use of an existing Tracer instance that you may have initialized anywhere in your code.
 
@@ -78,9 +78,9 @@ This makes use of an existing Tracer instance that you may have initialized anyw
         ...
     ```
 
-When executed, your middleware name will [appear in AWS X-Ray Trace details as](/core/tracer) `## middleware_name`.
+When executed, your middleware name will [appear in AWS X-Ray Trace details as](../core/tracer.md) `## middleware_name`.
 
-For advanced use cases, you can instantiate [Tracer](/core/tracer) inside your middleware, and add annotations as well as metadata for additional operational insights.
+For advanced use cases, you can instantiate [Tracer](../core/tracer.md) inside your middleware, and add annotations as well as metadata for additional operational insights.
 
 === "app.py"