From 4dcbcb22a8cc8ea9d12d9b17cd62bf64cd86a352 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jorge=20Puente=20Sarr=C3=ADn?= Date: Sun, 12 May 2013 15:10:08 -0500 Subject: [PATCH] GitHub is a proper noun --- README.rst | 2 +- archive/meta.build-system.rst | 6 +++--- source/meta/practices.txt | 2 +- themes/mongodb/layout.html | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.rst b/README.rst index 2bd2325a6e2..e1951ddd20e 100644 --- a/README.rst +++ b/README.rst @@ -17,7 +17,7 @@ of the documentation. You may also wish to install `Pygments examples. To contribute to the documentation please fork this repository on -github and issue a pull request. File issue reports or requests at the +GitHub and issue a pull request. File issue reports or requests at the `Documentation Jira Project `_. See the following documents within this repository that provide a more thorough overview of the documentation style, process, and overall diff --git a/archive/meta.build-system.rst b/archive/meta.build-system.rst index 1146d211b0c..048c3d8e503 100644 --- a/archive/meta.build-system.rst +++ b/archive/meta.build-system.rst @@ -100,11 +100,11 @@ Public Contributions (*Where public equals, anyone outside of the docs team, including 10gen engineers, other staff, and the community.*) -The "main" repository on github will have a master branch that tracks +The "main" repository on GitHub will have a master branch that tracks the "hyperalpha" branch. This is rebuilt regularly and is easily accessible on the web but is excluded from ``robots.txt`` and has no-follow links to avoid defusing the search results. Contributions -come in the form of edits directly on github, or pull requests. +come in the form of edits directly on GitHub, or pull requests. Then, with editing and review, changes from hyperalpha are batched and reviewed and merged into the "current" branch. The next section covers @@ -153,7 +153,7 @@ many cases) by pulling from git repositories and building from a specific git tag. The builds are then located (per driver) in versioned directories based on the tag name. A symbolic link named "current" points to the current version of the documentation. These -builds are then checked into the apidocs repo, pushed to github, and +builds are then checked into the apidocs repo, pushed to GitHub, and then a command is issued on the web servers to pull the apidocs repo, into the "public" directory for api.mongodb.org." diff --git a/source/meta/practices.txt b/source/meta/practices.txt index a0ab1008b57..c2504827cb8 100644 --- a/source/meta/practices.txt +++ b/source/meta/practices.txt @@ -29,7 +29,7 @@ Standards and Practices reviewers should have significant technical experience with the material covered in the documentation. -- All development and editorial work should transpire on github branches +- All development and editorial work should transpire on GitHub branches or forks that editors can then merge into the publication branches. diff --git a/themes/mongodb/layout.html b/themes/mongodb/layout.html index 30fb7330823..24e50abdd30 100644 --- a/themes/mongodb/layout.html +++ b/themes/mongodb/layout.html @@ -13,7 +13,7 @@ {%- endif -%} {%- macro githublink() -%} - Edit this Page + Edit this Page {%- endmacro -%} {%- macro jiralink() -%}