From 028561e6ff0aaa4da76a4aac59ae136f66060c98 Mon Sep 17 00:00:00 2001 From: Hossein Abbasi <16090309+hsnabszhdn@users.noreply.github.com> Date: Fri, 4 Jul 2025 14:02:57 +1000 Subject: [PATCH] Fix 'git' brand and trademark --- docs/specs/devcontainer-features-distribution.md | 6 +++--- docs/specs/devcontainer-reference.md | 2 +- docs/specs/devcontainer-templates-distribution.md | 8 ++++---- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/specs/devcontainer-features-distribution.md b/docs/specs/devcontainer-features-distribution.md index e2c09615..606dfac7 100644 --- a/docs/specs/devcontainer-features-distribution.md +++ b/docs/specs/devcontainer-features-distribution.md @@ -15,9 +15,9 @@ Goals include: ## Source code -Features source code is stored in a git repository. +Features source code is stored in a Git repository. -For ease of authorship and maintenance, [1..n] features can share a single git repository. This set of features is referred to as a "collection," and will share the same [`devcontainer-collection.json`](#devcontainer-collection.json) file and "namespace" (eg. `/`). +For ease of authorship and maintenance, [1..n] features can share a single Git repository. This set of features is referred to as a "collection," and will share the same [`devcontainer-collection.json`](#devcontainer-collection.json) file and "namespace" (eg. `/`). Source code for the set follows the example file structure below: @@ -117,7 +117,7 @@ done ``` -The "namespace" is the globally identifiable name for the collection of Features. (eg: `owner/repo` for the source code's git repository). +The "namespace" is the globally identifiable name for the collection of Features. (eg: `owner/repo` for the source code's Git repository). The auto-generated `devcontainer-collection.json` is pushed to the registry with the same `namespace` as above and no accompanying `feature` name. The collection file is always tagged as `latest`. diff --git a/docs/specs/devcontainer-reference.md b/docs/specs/devcontainer-reference.md index 0944621a..e129b1fb 100644 --- a/docs/specs/devcontainer-reference.md +++ b/docs/specs/devcontainer-reference.md @@ -283,4 +283,4 @@ Each entry in the `object` will be run in parallel during that lifecycle step. #### **Project Workspace Folder** -The **project workspace folder** is where an implementing tool should begin to search for `devcontainer.json` files. If the target project on disk is using git, the **project workspace folder** is typically the root of the git repository. +The **project workspace folder** is where an implementing tool should begin to search for `devcontainer.json` files. If the target project on disk is using Git, the **project workspace folder** is typically the root of the Git repository. diff --git a/docs/specs/devcontainer-templates-distribution.md b/docs/specs/devcontainer-templates-distribution.md index d058bf10..436279a8 100644 --- a/docs/specs/devcontainer-templates-distribution.md +++ b/docs/specs/devcontainer-templates-distribution.md @@ -11,11 +11,11 @@ Goals include: ## Source code -A Template's source code is stored in a git repository. +A Template's source code is stored in a Git repository. -For ease of authorship and maintenance, [1..n] Templates can share a single git repository. This set of Templates is referred to as a "collection," and will share the same [`devcontainer-collection.json`](#devcontainer-collection.json) file and "namespace" (eg. `/`). +For ease of authorship and maintenance, [1..n] Templates can share a single Git repository. This set of Templates is referred to as a "collection," and will share the same [`devcontainer-collection.json`](#devcontainer-collection.json) file and "namespace" (eg. `/`). -> **Note:** Templates and [Features](./devcontainer-features.md) should be placed in different git repositories. +> **Note:** Templates and [Features](./devcontainer-features.md) should be placed in different Git repositories. Source code for a set of Templates follows the example file structure below: @@ -114,7 +114,7 @@ done ``` -The "namespace" is the globally identifiable name for the collection of Templates. (eg: `owner/repo` for the source code's git repository). +The "namespace" is the globally identifiable name for the collection of Templates. (eg: `owner/repo` for the source code's Git repository). The auto-generated `devcontainer-collection.json` is pushed to the registry with the same `namespace` as above and no accompanying `template` name. The collection file is always tagged as `latest`.