Skip to content

Commit 7e1ca3c

Browse files
authored
Update content-style-guide.md
1 parent 75c3d28 commit 7e1ca3c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

contributing/content-style-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -387,7 +387,7 @@ For more information, see "[Using SHAs](https://docs.github.com/en/actions/learn
387387

388388
Always use "GitHub Codespaces" (`{% data variables.product.prodname_github_codespaces %}`) as the product name, not just "Codespaces". This helps to avoid confusion with "codespaces" (lowercase c), which refers to instances of remote coding workspaces created with GitHub Codespaces.
389389

390-
Always use "dev container" (or its longer form "development container) and not "devcontainer" (one word), except in file/path names. Although "devcontainer" is very commonly used internally within GitHub, Microsoft have specifically asked us not to use this form in publicly visible places as the single word could be considered its own brand, which we want to avoid, and we also want to be consistent with the two-word form used in [the Visual Studio Code documentation](https://code.visualstudio.com/docs/remote/create-dev-container#_path-to-creating-a-dev-container).
390+
Always use "dev container" (or its longer form "development container) and not "devcontainer" (one word), except in file/path names. The single word could form could be considered a brand, which we want to avoid, and we also want to be consistent with the two-word form used in [the Visual Studio Code documentation](https://code.visualstudio.com/docs/remote/create-dev-container#_path-to-creating-a-dev-container).
391391

392392
## Punctuation
393393

0 commit comments

Comments
 (0)