diff --git a/content/en/blog/2023/testing-otel-demo/index.md b/content/en/blog/2023/testing-otel-demo/index.md
index 076894b997a2..56b0ef4c21ad 100644
--- a/content/en/blog/2023/testing-otel-demo/index.md
+++ b/content/en/blog/2023/testing-otel-demo/index.md
@@ -1,5 +1,5 @@
 ---
-title: Testing the OpenTelemetry Demo with Trace-based Tests
+title: Trace-based Testing the OpenTelemetry Demo
 linkTitle: Testing the OTel Demo
 date: 2023-07-18
 author: '[Daniel Dias](https://github.com/danielbdias) (Tracetest)'
@@ -28,7 +28,7 @@ microservices results and its telemetry. This resulted in
 [adding trace-based tests to the demo](https://github.com/open-telemetry/opentelemetry-demo/pull/877).
 
 This article describes how trace-based tests were added to the OpenTelemetry
-demo. It discusses the challenges we faced while building it, the outcomes, and
+Demo. It discusses the challenges we faced while building it, the outcomes, and
 how it can help the OpenTelemetry community test the demo and add features with
 greater confidence.
 
@@ -47,7 +47,7 @@ To perform a trace-based test, we execute an operation against the system, which
 generates a trace, following these steps:
 
 1. Trigger an operation against the system and collect its output and trace id
-   generated from the operation;
+   generated from the operation.
 2. Wait for the system to report the entire trace to the telemetry data store;
 3. Collect the trace data generated by the system during the operation. This
    data should include timing information, as well as any errors or exceptions
@@ -73,10 +73,10 @@ changes do not result in unwanted outcomes in both the results and telemetry.
 Our testing mainly focused on the services involved in the main workflow of the
 system, which includes:
 
-1. A user navigating to the shop;
-2. Selecting a product;
-3. Deciding to make a purchase;
-4. And, completing the checkout process.
+1. A user navigating to the shop
+2. Selecting a product
+3. Deciding to make a purchase
+4. Completing the checkout process
 
 We structured two types of tests based on
 [tests that currently exist in the demo](/docs/demo/tests/):