Merge branch 'master' into project_name

compose-spec · Nov 20, 2021 · 0257a0d · 0257a0d
2 parents 355447e + a5a952e
commit 0257a0d
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/build.md b/build.md
@@ -64,8 +64,8 @@ services:
   backend:
     image: awesome/database
     build:
-        context: backend
-        dockerfile: ../backend.Dockerfile
+      context: backend
+      dockerfile: ../backend.Dockerfile
 
   custom:
     build: ~/custom

diff --git a/spec.md b/spec.md
@@ -221,7 +221,7 @@ Top-level `version` property is defined by the specification for backward compat
 A Compose implementation SHOULD NOT use this version to select an exact schema to validate the Compose file, but
 prefer the most recent schema at the time it has been designed.
 
-Compose implementations SHOULD validate they can fully parse the Compose file. If some fields are unknown, typically
+Compose implementations SHOULD validate whether they can fully parse the Compose file. If some fields are unknown, typically
 because the Compose file was written with fields defined by a newer version of the specification, Compose implementations
 SHOULD warn the user. Compose implementations MAY offer options to ignore unknown fields (as defined by ["loose"](#Requirements-and-optional-attributes) mode).