diff --git a/docs/tracing/faq/logging_and_viewing.mdx b/docs/tracing/faq/logging_and_viewing.mdx
index 4c6ff06f..adbce104 100644
--- a/docs/tracing/faq/logging_and_viewing.mdx
+++ b/docs/tracing/faq/logging_and_viewing.mdx
@@ -45,13 +45,14 @@ Please follow the [Setup](/) guide to learn how to sign up and create an API key
 By default, the traces will be logged to a project named `default`.
 To log traces to a different project, see [this section](/tracing/faq/customizing_trace_attributes#logging-to-a-specific-project).
 :::
+
 :::note
 Please make sure to set the `LANGCHAIN_API_KEY` environment variable to your API key before running the examples below.
 Additionally, you will need to set `LANGCHAIN_TRACING_V2='true'` if you plan to use either:
 
 - LangChain (Python or JS)
 - `@traceable` decorator or `wrap_openai` method in the Python SDK
-  :::
+:::
 
 <CodeTabs
   tabs={[
@@ -260,6 +261,7 @@ This works for the `traceable` decorator and `RunTree` objects.
 LangSmith supports distributed tracing out of the box, linking runs within a trace across services using context propagation headers (`langsmith-trace` and optional `baggage` for metadata/tags).
 
 Example client-server setup:
+
 - Trace starts on client
 - Continues on server
 
@@ -303,9 +305,6 @@ async def fake_route(request: Request):
 
 ```
 
-
-
-
 ### Turning off tracing
 
 If you've decided you no longer want to trace your runs, you can remove the environment variables configured to start tracing in the first place.