From fc871567cab746ea65ddd3b44645d3fa0a404fd6 Mon Sep 17 00:00:00 2001
From: Bri Wylde <92327786+briwylde08@users.noreply.github.com>
Date: Fri, 20 Oct 2023 10:10:04 -0600
Subject: [PATCH] editorial in Update hello-world.mdx

---
 docs/getting-started/hello-world.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/getting-started/hello-world.mdx b/docs/getting-started/hello-world.mdx
index f4c56b40..5221e81a 100644
--- a/docs/getting-started/hello-world.mdx
+++ b/docs/getting-started/hello-world.mdx
@@ -376,11 +376,11 @@ soroban contract invoke ... -- hello --help
 
 ### Diagnostic Events
 
-You will also notice here (and with any other contract run in the sandbox environment) some diagnostic output will be displayed on the screen. This is because `soroban-cli` automatically sets the diagnostic level to "Debug" for contracts running in the sandbox.
+You will also notice here (and with any other contract run in the sandbox environment) that some diagnostic output will be displayed on the screen. This is because the `soroban-cli` automatically sets the diagnostic level to "Debug" for contracts running in the sandbox.
 
 Here, we'll see two diagnostic events were emitted by our contract invocation:
 
-1. First is a `fn_call` diagnostic event. It tells you the _kind_ of event, the contract ID which will be called, the name of the function being called, and a vector of the arguments passed to the function. A (greatly simplified) version of this event's body would look like this:
+1. First is a `fn_call` diagnostic event. It tells you the _kind_ of event, the contract ID that will be called, the name of the function being called, and a vector of the arguments passed to the function. A (greatly simplified) version of this event's body would look like this:
 
 ```
 {