From cbd2ae8ad7f71d93f43d44d7b530d100c308f4b6 Mon Sep 17 00:00:00 2001 From: Hossein Abbasi <16090309+hsnabszhdn@users.noreply.github.com> Date: Fri, 4 Jul 2025 13:43:11 +1000 Subject: [PATCH] Remove articles for backtick'd words --- docs/specs/devcontainer-features-distribution.md | 2 +- docs/specs/devcontainer-templates-distribution.md | 2 +- docs/specs/devcontainer-templates.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/specs/devcontainer-features-distribution.md b/docs/specs/devcontainer-features-distribution.md index e2c09615..37e623e8 100644 --- a/docs/specs/devcontainer-features-distribution.md +++ b/docs/specs/devcontainer-features-distribution.md @@ -92,7 +92,7 @@ An OCI registry that implements the [OCI Artifact Distribution Specification](ht Each packaged feature is pushed to the registry following the naming convention `//[:version]`, where version is the major, minor, and patch version of the Feature, according to the semver specification. -> **Note:** The `namespace` is a unique identifier for the collection of Features. There are no strict rules for the `namespace`; however, one pattern is to set `namespace` equal to source repository's `/`. The `namespace` should be lowercase, following [the regex provided in the OCI specification](https://github.com/opencontainers/distribution-spec/blob/main/spec.md#pulling-manifests). +> **Note:** `namespace` is a unique identifier for the collection of Features. There are no strict rules for `namespace`; however, one pattern is to set `namespace` equal to source repository's `/`. The `namespace` should be lowercase, following [the regex provided in the OCI specification](https://github.com/opencontainers/distribution-spec/blob/main/spec.md#pulling-manifests). A custom media type `application/vnd.devcontainers` and `application/vnd.devcontainers.layer.v1+tar` are used as demonstrated below. diff --git a/docs/specs/devcontainer-templates-distribution.md b/docs/specs/devcontainer-templates-distribution.md index d058bf10..dc5f78de 100644 --- a/docs/specs/devcontainer-templates-distribution.md +++ b/docs/specs/devcontainer-templates-distribution.md @@ -89,7 +89,7 @@ An OCI registry that implements the [OCI Artifact Distribution Specification](ht Each packaged Template is pushed to the registry following the naming convention `//[:version]`, where version is the major, minor, and patch version of the Template, according to the semver specification. -> **Note:** The `namespace` is a unique identifier for the collection of Templates and must be different than the collection of [Features](./devcontainer-features.md). There are no strict rules for the `namespace`; however, one pattern is to set `namespace` equal to source repository's `/`. +> **Note:** `namespace` is a unique identifier for the collection of Templates and must be different than the collection of [Features](./devcontainer-features.md). There are no strict rules for `namespace`; however, one pattern is to set `namespace` equal to source repository's `/`. A custom media type `application/vnd.devcontainers` and `application/vnd.devcontainers.layer.v1+tar` are used as demonstrated below. diff --git a/docs/specs/devcontainer-templates.md b/docs/specs/devcontainer-templates.md index 7e53f6e4..fc97fce5 100644 --- a/docs/specs/devcontainer-templates.md +++ b/docs/specs/devcontainer-templates.md @@ -2,7 +2,7 @@ **Development Container Templates** are source files packaged together that encode configuration for a complete development environment. A Template can be used in a new or existing project, and a [supporting tool](https://containers.dev/supporting) will use the configuration from the Template to build a development container. -The configuration is placed in a [`.devcontainer/devcontainer.json`](/docs/specs/devcontainer-reference.md#devcontainerjson) which can also reference other files within the Template. A Template can also provide additional source files (eg: boilerplate code or a [lifecycle script](https://containers.dev/implementors/json_reference/#lifecycle-scripts). +The configuration is placed in [`.devcontainer/devcontainer.json`](/docs/specs/devcontainer-reference.md#devcontainerjson) which can also reference other files within the Template. A Template can also provide additional source files (eg: boilerplate code or a [lifecycle script](https://containers.dev/implementors/json_reference/#lifecycle-scripts). Template metadata is captured by a `devcontainer-template.json` file in the root folder of the Template.