Browse code

Fix GitHub spelling

Signed-off-by: Frieder Bluemle <frieder.bluemle@gmail.com>

Frieder Bluemle authored on 2017/10/05 01:38:09
Showing 13 changed files
... ...
@@ -1,4 +1,4 @@
1
-# Github code owners
1
+# GitHub code owners
2 2
 # See https://help.github.com/articles/about-codeowners/
3 3
 #
4 4
 # KEEP THIS FILE SORTED. Order is important. Last match takes precedence.
... ...
@@ -264,7 +264,7 @@
264 264
 	[people.cpuguy83]
265 265
 	Name = "Brian Goff"
266 266
 	Email = "cpuguy83@gmail.com"
267
-	Github = "cpuguy83"
267
+	GitHub = "cpuguy83"
268 268
 
269 269
 	[people.chanwit]
270 270
 	Name = "Chanwit Kaewkasi"
... ...
@@ -7,8 +7,8 @@ redirect_from:
7 7
 - /reference/api/docker_remote_api_v1.18/
8 8
 ---
9 9
 
10
-<!-- This file is maintained within the docker/docker Github
11
-     repository at https://github.com/docker/docker/. Make all
10
+<!-- This file is maintained within the moby/moby GitHub
11
+     repository at https://github.com/moby/moby/. Make all
12 12
      pull requests against that repo. If you see this file in
13 13
      another repository, consider it read-only there, as it will
14 14
      periodically be overwritten by the definitive file. Pull
... ...
@@ -7,8 +7,8 @@ redirect_from:
7 7
 - /reference/api/docker_remote_api_v1.19/
8 8
 ---
9 9
 
10
-<!-- This file is maintained within the docker/docker Github
11
-     repository at https://github.com/docker/docker/. Make all
10
+<!-- This file is maintained within the moby/moby GitHub
11
+     repository at https://github.com/moby/moby/. Make all
12 12
      pull requests against that repo. If you see this file in
13 13
      another repository, consider it read-only there, as it will
14 14
      periodically be overwritten by the definitive file. Pull
... ...
@@ -7,8 +7,8 @@ redirect_from:
7 7
 - /reference/api/docker_remote_api_v1.20/
8 8
 ---
9 9
 
10
-<!-- This file is maintained within the docker/docker Github
11
-     repository at https://github.com/docker/docker/. Make all
10
+<!-- This file is maintained within the moby/moby GitHub
11
+     repository at https://github.com/moby/moby/. Make all
12 12
      pull requests against that repo. If you see this file in
13 13
      another repository, consider it read-only there, as it will
14 14
      periodically be overwritten by the definitive file. Pull
... ...
@@ -7,8 +7,8 @@ redirect_from:
7 7
 - /reference/api/docker_remote_api_v1.21/
8 8
 ---
9 9
 
10
-<!-- This file is maintained within the docker/docker Github
11
-     repository at https://github.com/docker/docker/. Make all
10
+<!-- This file is maintained within the moby/moby GitHub
11
+     repository at https://github.com/moby/moby/. Make all
12 12
      pull requests against that repo. If you see this file in
13 13
      another repository, consider it read-only there, as it will
14 14
      periodically be overwritten by the definitive file. Pull
... ...
@@ -7,8 +7,8 @@ redirect_from:
7 7
 - /reference/api/docker_remote_api_v1.22/
8 8
 ---
9 9
 
10
-<!-- This file is maintained within the docker/docker Github
11
-     repository at https://github.com/docker/docker/. Make all
10
+<!-- This file is maintained within the moby/moby GitHub
11
+     repository at https://github.com/moby/moby/. Make all
12 12
      pull requests against that repo. If you see this file in
13 13
      another repository, consider it read-only there, as it will
14 14
      periodically be overwritten by the definitive file. Pull
... ...
@@ -7,8 +7,8 @@ redirect_from:
7 7
 - /reference/api/docker_remote_api_v1.23/
8 8
 ---
9 9
 
10
-<!-- This file is maintained within the docker/docker Github
11
-     repository at https://github.com/docker/docker/. Make all
10
+<!-- This file is maintained within the moby/moby GitHub
11
+     repository at https://github.com/moby/moby/. Make all
12 12
      pull requests against that repo. If you see this file in
13 13
      another repository, consider it read-only there, as it will
14 14
      periodically be overwritten by the definitive file. Pull
... ...
@@ -7,8 +7,8 @@ redirect_from:
7 7
 - /reference/api/docker_remote_api_v1.24/
8 8
 ---
9 9
 
10
-<!-- This file is maintained within the docker/docker Github
11
-     repository at https://github.com/docker/docker/. Make all
10
+<!-- This file is maintained within the moby/moby GitHub
11
+     repository at https://github.com/moby/moby/. Make all
12 12
      pull requests against that repo. If you see this file in
13 13
      another repository, consider it read-only there, as it will
14 14
      periodically be overwritten by the definitive file. Pull
... ...
@@ -4,8 +4,8 @@ description: "Documentation of changes that have been made to Engine API."
4 4
 keywords: "API, Docker, rcli, REST, documentation"
5 5
 ---
6 6
 
7
-<!-- This file is maintained within the docker/docker Github
8
-     repository at https://github.com/docker/docker/. Make all
7
+<!-- This file is maintained within the moby/moby GitHub
8
+     repository at https://github.com/moby/moby/. Make all
9 9
      pull requests against that repo. If you see this file in
10 10
      another repository, consider it read-only there, as it will
11 11
      periodically be overwritten by the definitive file. Pull
... ...
@@ -143,7 +143,7 @@ func (s *DockerSuite) TestHealth(c *check.C) {
143 143
 
144 144
 }
145 145
 
146
-// Github #33021
146
+// GitHub #33021
147 147
 func (s *DockerSuite) TestUnsetEnvVarHealthCheck(c *check.C) {
148 148
 	testRequires(c, DaemonIsLinux) // busybox doesn't work on Windows
149 149
 
... ...
@@ -45,7 +45,7 @@ defined by a ROADMAP.md file at the root of the repository).
45 45
 - The earlier a PR is opened, the more time the maintainers have to review. For
46 46
 example, if a PR is opened the day before the freeze date, it’s very unlikely
47 47
 that it will be merged for the release.
48
-- Constant communication with the maintainers (mailing-list, IRC, Github issues,
48
+- Constant communication with the maintainers (mailing-list, IRC, GitHub issues,
49 49
 etc.) allows to get early feedback on the design before getting into the
50 50
 implementation, which usually reduces the time needed to discuss a changeset.
51 51
 - If the code is commented, fully tested and by extension follows every single
... ...
@@ -68,7 +68,7 @@ the next appropriate stage:
68 68
 
69 69
  - Has DCO
70 70
  - Contains sufficient justification (e.g., usecases) for the proposed change
71
- - References the Github issue it fixes (if any) in the commit or the first Github comment
71
+ - References the GitHub issue it fixes (if any) in the commit or the first GitHub comment
72 72
 
73 73
 Possible transitions from this state:
74 74