From b41c6b302a8d4b585de01e2bb8077af424f1eb64 Mon Sep 17 00:00:00 2001 From: Hang Yan Date: Mon, 4 Oct 2021 16:22:30 +0800 Subject: [PATCH 1/3] Small typo fix Signed-off-by: Hang Yan --- spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.md b/spec.md index ac0498bd..8387204e 100644 --- a/spec.md +++ b/spec.md @@ -219,7 +219,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 before 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). From 61e518dbeca74ac07a056bcb60a9ac68221aa378 Mon Sep 17 00:00:00 2001 From: Hang Yan Date: Fri, 8 Oct 2021 10:01:29 +0800 Subject: [PATCH 2/3] Update english sentence Signed-off-by: Hang Yan --- spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.md b/spec.md index 8387204e..1cc1681a 100644 --- a/spec.md +++ b/spec.md @@ -219,7 +219,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 before 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). From a5a952ea97577169fff9f0b26854a9d92c3437ee Mon Sep 17 00:00:00 2001 From: Tim Way <1091435+timway@users.noreply.github.com> Date: Tue, 12 Oct 2021 17:17:53 -0500 Subject: [PATCH 3/3] Minor Spacing Adjustment While not required by the spec the rest of the documents use 2 spaces for nesting in YAML code blocks. This snuck through at 4. Signed-off-by: Tim Way <1091435+timway@users.noreply.github.com> --- build.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/build.md b/build.md index ce303537..eeb7413f 100644 --- 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