diff --git a/documentation/content/en/books/porters-handbook/special/chapter.adoc b/documentation/content/en/books/porters-handbook/special/chapter.adoc
--- a/documentation/content/en/books/porters-handbook/special/chapter.adoc
+++ b/documentation/content/en/books/porters-handbook/special/chapter.adoc
@@ -713,7 +713,7 @@
 .Creating a Port for a Go Modules Based Application
 [example]
 ====
-In most cases, it is sufficient to set `GO_MODULE` variable to the value specified by `module` directive in `go.mod`:
+In most cases, it is sufficient to set the `GO_MODULE` variable to the value specified by the `module` directive in `go.mod`:
 
 [.programlisting]
 ....
diff --git a/documentation/content/en/books/porters-handbook/uses/chapter.adoc b/documentation/content/en/books/porters-handbook/uses/chapter.adoc
--- a/documentation/content/en/books/porters-handbook/uses/chapter.adoc
+++ b/documentation/content/en/books/porters-handbook/uses/chapter.adoc
@@ -520,7 +520,7 @@
 The build process is controlled by several variables:
 
 `GO_MODULE`::
-The name of the application module as specified by `module` directive in `go.mod`. In most cases, this is the only requred variable for ports that use Go modules.
+The name of the application module as specified by the `module` directive in `go.mod`. In most cases, this is the only required variable for ports that use Go modules.
 
 `GO_PKGNAME`::
 The name of the Go package when building in GOPATH mode. This is the directory that will be created in `${GOPATH}/src`. If not set explicitly and `GH_SUBDIR` or `GL_SUBDIR` is present, `GO_PKGNAME` will be inferred from it. It is not needed when building in modules-aware mode.