diff --git a/compose/compose-file/build.md b/compose/compose-file/build.md
index 1a9eb13c35..aa86248a9a 100644
--- a/compose/compose-file/build.md
+++ b/compose/compose-file/build.md
@@ -274,13 +274,13 @@ build:
 
 ### no_cache
 
-`no_cache` disables image builder cache and enforce a full rebuild from source for all image layers. This only
+`no_cache` disables image builder cache and enforces a full rebuild from source for all image layers. This only
 applies to layers declared in the Dockerfile, referenced images COULD be retrieved from local image store whenever tag
 has been updated on registry (see [pull](#pull)).
 
 ### pull
 
-`pull` require the image builder to pull referenced images (`FROM` Dockerfile directive), even if those are already 
+`pull` requires the image builder to pull referenced images (`FROM` Dockerfile directive), even if those are already 
 available in the local image store.
 
 ### shm_size
@@ -315,7 +315,7 @@ build:
 different syntax variants are supported: the short syntax and the long syntax.
 
 Compose implementations MUST report an error if the secret isn't defined in the
-[`secrets`](index.md#secrets-top-level-element) section of this Compose file.
+[`secrets`](index.md#secrets-top-level-element) section of the Compose file.
 
 #### Short syntax
 
@@ -356,9 +356,9 @@ the service's containers.
   The writable bit MUST be ignored if set. The executable bit MAY be set.
 
 The following example sets the name of the `server-certificate` secret file to `server.crt`
-within the container, sets the mode to `0440` (group-readable) and sets the user and group
+within the container, sets the mode to `0440` (group-readable), and sets the user and group
 to `103`. The value of `server-certificate` secret is provided by the platform through a lookup and
-the secret lifecycle not directly managed by the Compose implementation.
+the secret lifecycle is not directly managed by the Compose implementation.
 
 ```yml
 services:
@@ -378,7 +378,7 @@ secrets:
 
 Service builds MAY be granted access to multiple secrets. Long and short syntax for secrets MAY be used in the
 same Compose file. Defining a secret in the top-level `secrets` MUST NOT imply granting any service build access to it.
-Such grant must be explicit within service specification as [secrets](index.md#secrets) service element.
+Such grant must be explicit within the service specification as a [secrets](index.md#secrets) service element.
 
 ### tags