Skip to content

GitHub is a proper noun #983

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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 <https://jira.mongodb.org/browse/DOCS>`_.
See the following documents within this repository that provide a more
thorough overview of the documentation style, process, and overall
Expand Down
6 changes: 3 additions & 3 deletions archive/meta.build-system.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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."

Expand Down
2 changes: 1 addition & 1 deletion source/meta/practices.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion themes/mongodb/layout.html
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
{%- endif -%}

{%- macro githublink() -%}
<a href="https://github.com/mongodb/{{theme_repo_name}}/blob/{{theme_branch}}/source/{{pagename}}.txt" target="_blank" title="Edit {{pagename}}.txt on github">Edit this Page</a>
<a href="https://github.com/mongodb/{{theme_repo_name}}/blob/{{theme_branch}}/source/{{pagename}}.txt" target="_blank" title="Edit {{pagename}}.txt on GitHub">Edit this Page</a>
{%- endmacro -%}

{%- macro jiralink() -%}
Expand Down