diff --git a/sample-apps/java-sample-app/README.md b/sample-apps/java-sample-app/README.md
index 6f5915d0..98d82679 100644
--- a/sample-apps/java-sample-app/README.md
+++ b/sample-apps/java-sample-app/README.md
@@ -74,7 +74,7 @@ This application also tries to demonstrate how the correlation between traces an
 1. Define the resource attribute `aws.log.group.names`. [Reference](https://opentelemetry.io/docs/reference/specification/resource/semantic_conventions/cloud_provider/aws/logs/)
 2. Inject the trace id in the logs. The following string must be present in the log line `AWS-XRAY-TRACE-ID: TraceID@EntityID`. Example: `AWS-XRAY-TRACE-ID: 1-5d77f256-19f12e4eaa02e3f76c78f46a@1ce7df03252d99e1`. [Reference](https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-java-configuration.html#xray-sdk-java-configuration-logging).
 
-Both the manual and auto instrumentation applications are implementing the steps bellow. They use different mechanisms to do that:
+Both the manual and auto instrumentation applications are implementing the steps below. They use different mechanisms to do that:
 
 1. Resource attribute. This is configurable using the system property `adot.sampleapp.loggroup`. The default value is `sample-app-trace-logs`. Each application type use a different mechanism to set this resource attribute.
   * Manual instrumentation - During SDK initialization.
@@ -82,4 +82,4 @@ Both the manual and auto instrumentation applications are implementing the steps
 2. Trace id injection.
   * Both applications use log4j Mapped Diagnostic Context (MDC). The format of the log is defined in the `log4j2.xml` file in each application directory.
 
-We are also including an example configuration file in `cw-agent.json` so that cloudwatch agent can capture the logs of the sample application when running locally.
\ No newline at end of file
+We are also including an example configuration file in `cw-agent.json` so that cloudwatch agent can capture the logs of the sample application when running locally.