diff --git a/docs/tutorials/instrumenting_http_server_in_go.md b/docs/tutorials/instrumenting_http_server_in_go.md
index a5cf455fe..b26c33459 100644
--- a/docs/tutorials/instrumenting_http_server_in_go.md
+++ b/docs/tutorials/instrumenting_http_server_in_go.md
@@ -3,7 +3,7 @@ title: Instrumenting HTTP server written in Go
 sort_rank: 3
 ---
 
-In this tutorial we will create a simple Go HTTP server and instrumentation it by adding a counter
+In this tutorial, we will create a simple Go HTTP server and instrument it by adding a counter
 metric to keep count of the total number of requests processed by the server.
 
 Here we have a simple HTTP server with `/ping` endpoint which returns `pong` as response.
@@ -39,7 +39,7 @@ Now open `http://localhost:8090/ping` in your browser and you must see `pong`.
 [![Server](/assets/docs/tutorial/server.png)](/assets/docs/tutorial/server.png)
 
 
-Now lets add a metric to the server which will instrument the number of requests made to the ping endpoint, the counter metric type is suitable for this as we know the request count doesn’t go down and only increases.
+Now let's add a metric to the server which will instrument the number of requests made to the ping endpoint. The counter metric type is suitable for this as we know the request count doesn’t go down and only increases.
 
 Create a Prometheus counter
 
@@ -53,14 +53,14 @@ func newMetrics(reg prometheus.Registerer) *metrics {
 		pingCounter: promauto.With(reg).NewCounter(
 			prometheus.CounterOpts{
 				Name: "ping_request_count",
-				Help: "No of request handled by Ping handler",
+				Help: "No of requests handled by Ping handler",
 			}),
 	}
 	return m
 }
 ```
 
-Next lets update the ping Handler to increase the count of the counter using `metrics.pingCounter.Inc()`.
+Next, let's update the ping Handler to increase the count of the counter using `metrics.pingCounter.Inc()`.
 
 ```go
 func ping(m *metrics) func(w http.ResponseWriter, req *http.Request) {
@@ -71,7 +71,7 @@ func ping(m *metrics) func(w http.ResponseWriter, req *http.Request) {
 }
 ```
 
-Then register the metrics (in this case only one counter) to a Prometheus Register and expose the metrics.
+Then register the metrics (in this case, only one counter) with a Prometheus registry and expose the metrics.
 
 ```go
 func main() {
@@ -84,12 +84,11 @@ func main() {
 }
 ```
 
-The `prometheus.MustRegister` function registers the pingCounter to the default Register.
-To expose the metrics the Go Prometheus client library provides the promhttp package.
-`promhttp.Handler()` provides a `http.Handler` which exposes the metrics registered in the Default Register.
+The `prometheus.MustRegister` function registers the pingCounter with the default registry.
+To expose the metrics, the Go Prometheus client library provides the promhttp package.
+`promhttp.Handler()` provides an `http.Handler` which exposes the metrics registered in the default registry.
 
-The sample code depends on the
-The sample code depends on the
+The sample code is now:
 
 ```go
 package main
@@ -142,13 +141,13 @@ go mod tidy
 go run server.go
 ```
 
-Now hit the localhost:8090/ping endpoint a couple of times and sending a request to localhost:8090 will provide the metrics.
+Now hit the localhost:8090/ping endpoint a couple of times and then send a request to localhost:8090/metrics to see the metrics.
 
 [![Ping Metric](/assets/docs/tutorial/ping_metric.png)](/assets/docs/tutorial/ping_metric.png)
 
-Here the `ping_request_count` shows that `/ping` endpoint was called 3 times.
+Here, the `ping_request_count` shows that the `/ping` endpoint was called 3 times.
 
-The Default Register comes with a collector for go runtime metrics and that is why we see other metrics like `go_threads`, `go_goroutines` etc.
+The default registry comes with a collector for Go runtime metrics, and that is why we see other metrics like `go_threads`, `go_goroutines`, etc.
 
 We have built our first metric exporter. Let’s update our Prometheus config to scrape the metrics from our server.