Fix Minor Issues with OTel Blogs & Document Yarn Setup Step (#2191)

* docs: add yarn setup step to readme

* fix: address minor issues in otel logs blog

* fix: fix typo and logical error in comment

* chore: move collector video at the end of collector section

* fix: remove formatting changes

* fix: remove auto-commit formatting changes

* fix: python indentation in example

Author: dhruv-signoz

README.md

@@ -14,34 +14,40 @@
    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
    ```
 
-2. Install and use the correct Node.js version by running the following commands in the project directory:
+2. Install Yarn if you haven't already:
+
+   ```bash
+   npm install -g yarn
+   ```
+
+3. Install and use the correct Node.js version by running the following commands in the project directory:
 
    ```bash
    nvm install
    nvm use
    ```
 
-3. Install dependencies:
+4. Install dependencies:
 
    ```bash
    yarn install
    ```
 
-4. Build the project to ensure there are no errors:
+5. Build the project to ensure there are no errors:
 
    ```bash
    yarn build
    ```
 
    This will create a `build` directory with the production build of the website. Check the output for any errors.
 
-5. Start the development server:
+6. Start the development server:
 
    ```bash
    yarn dev
    ```
 
-6. Open your browser and navigate to `http://localhost:3000` to view the website locally.
+7. Open your browser and navigate to `http://localhost:3000` to view the website locally.
 
 ### Git Hooks
 

data/blog/opentelemetry-collector-complete-guide.mdx

@@ -25,10 +25,6 @@ This guide will provide a comprehensive overview of the OpenTelemetry Collector,
 
 <a href="https://opentelemetry.io/" rel="noopener noreferrer">OpenTelemetry</a> is an open-source observability framework, incubated by the Cloud Native Computing Foundation (<a href="https://www.cncf.io/" rel="noopener noreferrer">CNCF</a>), that standardizes how telemetry data (logs, metrics, traces) is generated and collected. After instrumenting your applications with OpenTelemetry SDKs, the Collector is the next critical piece for managing that data.
 
-Check out the video for a quick walkthrough of OpenTelemetry Collector.
-
-<YouTube id="KFesgjzK3gk" mute={false}/>
-
 ## What is the OpenTelemetry Collector?
 
 In very simple words, the collector is an agent that sits between your instrumented services, collects the telemetry data that is emitted by the services, processes it and sends it to an observability backend.  
@@ -39,6 +35,10 @@ The below animation shows the flow of data through the collector. You can try th
 
 Apart from acting as a buffer, the collector also acts as a *translation layer;* it supports the native OpenTelemetry Protocol [OTLP] for ingesting data, but can also accept other formats [like Jaeger trace data or [Prometheus metrics](https://signoz.io/guides/what-are-the-4-types-of-metrics-in-prometheus/)] and translate them on the fly.
 
+Check out the video for a quick walkthrough of OpenTelemetry Collector.
+
+<YouTube id="KFesgjzK3gk" mute={false}/>
+
 ## Why Use an OpenTelemetry Collector?
 
 Using a Collector is a best practice for several key reasons:
@@ -263,4 +263,4 @@ With SigNoz, you can visualize all your logs, metrics, and traces in a single pa
 
 **[OpenTelemetry Logs - A Complete Introduction & Implementation](https://signoz.io/blog/opentelemetry-logs/)**<br />
 
-**[Monitor Nodejs Application with OpenTelemetry and SigNoz](https://signoz.io/opentelemetry/nodejs/)**<br />
+**[Monitor Nodejs Application with OpenTelemetry and SigNoz](https://signoz.io/opentelemetry/nodejs/)**<br />

data/blog/opentelemetry-logs.mdx

@@ -11,8 +11,6 @@ keywords: [opentelemetry logs,opentelemetry log,opentelemetry,logs correlation,o
 ---
 OpenTelemetry is a Cloud Native Computing Foundation(<a href = "https://www.cncf.io/" rel="noopener noreferrer nofollow" target="_blank" >CNCF</a>) incubating project aimed at standardizing the way we instrument applications for generating telemetry data(logs, metrics, and traces). OpenTelemetry aims to provide a vendor-agnostic observability framework that provides a set of tools, APIs, and SDKs to instrument applications.
 
-
-
 ![Cover Image](/img/blog/2023/10/otel-logs-cover.webp)
 
 Modern-day software systems are built with many pre-built components taken from the open source ecosystem like web frameworks, databases, HTTP clients, etc. Instrumenting such a software system in-house can pose a huge challenge. And using vendor-specific instrumentation agents can create a dependency. OpenTelemetry provides an open source instrumentation layer that can instrument various technologies like open source libraries, programming languages, databases, etc.
@@ -39,10 +37,9 @@ OpenTelemetry provides instrumentation libraries for your application. The devel
 
 <figure data-zoomable align='center'>
     <img src="/img/blog/2022/09/opentelemetry_architecture.webp" alt="OpenTelemetry Architecture"/>
-    <figcaption><i>How OpenTelemetry fits in an application architecture. OTel collector refers to OpenTelemetry Collector</i></figcaption>
+    <figcaption><i>How OpenTelemetry fits in an application architecture. OTel is the convenient short form for OpenTelemetry</i></figcaption>
 </figure>
 
-
 OpenTelemetry libraries can be used to generate logs, metrics, and traces. You can then collect these signals with OpenTelemetry Collector or send them to an observability backend of your choice. In this article, we will focus on [OpenTelemetry logs](https://signoz.io/comparisons/opentelemetry-events-vs-logs/). OpenTelemetry can be used to collect log data and process it. Let's explore OpenTelemetry logs further.
 
 [![Get Started - Free CTA](/img/blog/2024/01/opentelemetry-collector-try-signoz-cloud-cta.webp)](https://signoz.io/teams/)
@@ -220,7 +217,7 @@ In OpenTelemetry, there are two important context IDs for context propagation.
   A trace is a complete breakdown of a transaction as it travels through different components of a distributed system. Each trace gets a [trace ID](https://signoz.io/comparisons/opentelemetry-trace-id-vs-span-id/) that helps to correlate all events connected with a single trace.
 
 - **Span IDs**<br></br>
-  A trace consists of multiple spans. Each span represents a single unit of logical work in the trace data. Spans have span ids that are used to represent the parent-child relationship.
+  A trace consists of multiple spans. Each span represents a single unit of logical work in the trace data. Spans have span IDs that are used to represent the parent-child relationship.
     <figure data-zoomable align='center'>
     <img src="/img/blog/2025/09/otel-spans.webp" alt="Traces in SigNoz"/>
     <figcaption><i>A trace graph broken down into individual spans visualized as Flamegraphs and Gantt charts in SigNoz dashboard</i></figcaption>
@@ -269,17 +266,16 @@ from its SDK.
   Here's an example of using OpenTelemetry's [LoggingInstrumentor](https://opentelemetry-python-contrib.readthedocs.io/en/latest/instrumentation/logging/logging.html) to instrument the logging library to automatically add trace context in a Python application.
 
   ```python 
-
-      import logging
-        from opentelemetry.instrumentation.logging import LoggingInstrumentor
-        
-        # Instrument the logging library to automatically add trace context
-        LoggingInstrumentor().instrument(set_logging_format=True)
-        
-        # Now, any log created within an active trace will automatically
-        # include trace_id and span_id in its record.
-        logging.basicConfig(level=logging.INFO)
-        logging.info("User login successful.")
+  import logging
+  from opentelemetry.instrumentation.logging import LoggingInstrumentor
+  
+  # Instrument the logging library to automatically add trace context
+  LoggingInstrumentor().instrument(set_logging_format=True)
+  
+  # Now, any log created within an active trace will automatically
+  # include trace_id and span_id in its record.
+  logging.basicConfig(level=logging.INFO)
+  logging.info("User login successful.")
   ```
 
   **Example 2. Instrumenting in Java with a Log Appender**
@@ -311,16 +307,12 @@ application's source code as shown in the below example.
         </Root>
     </Loggers>
 </Configuration>
-
   ```
 
   As you can see, while the mechanism differs by language ecosystem (Handlers in Python, Appenders in Java), the
   underlying idea is the same, i.e, integrate the OpenTelemetry SDK with your existing logging framework to automatically enrich
   all your logs with invaluable trace context.
 
-
-
-
 ### Collecting third-party application log data
 
 Logs emitted by third-party applications running on the system are known as third-party application logs. The logs are typically written to stdout, files, or other specialized mediums. 
@@ -430,7 +422,7 @@ how you can perform log analytics. The logs tab in SigNoz has advanced features
 
 Your key step in any investigation during an escalation is to find the right logs. Instead of manually searching through tons of logs,
 you can use a query builder to filter logs based on any field in the OpenTelemetry log data model. 
-We recently made some improvements to the query builder to make it more, you can read more about it [here](https://signoz.io/blog/query-builder-v5/).
+We have recently overhauled the Query Builder, you can read more about it [here](https://signoz.io/blog/query-builder-v5/).
 
 For example, you can quickly find all logs with `SeverityText = ERROR` from your web-backend service that occurred in
 the last hour as shown in the below screenshot.
@@ -468,8 +460,6 @@ In SigNoz, the `TraceId` in a log record is a clickable link. Meaning, when you
     <figcaption><i>Correlating Logs with Traces in SigNoz</i></figcaption>
 </figure>
 
-
-
 ## Getting started with SigNoz
 
 <GetStartedSigNoz />
@@ -489,4 +479,4 @@ To get started with OpenTelemetry logs, install SigNoz and start experimenting b
 
 - [OpenTelemetry Collector - complete guide](https://signoz.io/blog/opentelemetry-collector-complete-guide/)
 
-- [Log Monitoring 101 Detailed Guide](https://signoz.io/blog/log-monitoring/)
+- [Log Monitoring 101 Detailed Guide](https://signoz.io/blog/log-monitoring/)