share/doc/homebrew: fix capitalization.

Reference.
* GitHub: https://github.com/about
* Xcode: https://developer.apple.com/xcode
* Zsh: http://www.zsh.org

Closes Homebrew/homebrew#37866.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
This commit is contained in:
Artur Dryomov 2015-03-19 19:10:20 +03:00 committed by Mike McQuaid
parent 3fd45673a5
commit 832c52db7e
3 changed files with 6 additions and 6 deletions

View File

@ -377,11 +377,11 @@ Now you just need to push back to GitHub.
If you havent forked Homebrew yet, [go to the repo and hit the fork button](https://github.com/Homebrew/homebrew). If you havent forked Homebrew yet, [go to the repo and hit the fork button](https://github.com/Homebrew/homebrew).
If you have already forked Homebrew on Github, then you can manually push (just make sure you have been pulling from the Homebrew/homebrew master): If you have already forked Homebrew on GitHub, then you can manually push (just make sure you have been pulling from the Homebrew/homebrew master):
git push git@github.com:myname/homebrew.git <what-you-called-your-branch> git push git@github.com:myname/homebrew.git <what-you-called-your-branch>
Now, please open a Pull Request (on your github repo page) for new and updated brews. Now, please open a Pull Request (on your GitHub repo page) for new and updated brews.
* One formula per commit; one commit per formula * One formula per commit; one commit per formula
* Keep merge commits out of the request * Keep merge commits out of the request
@ -593,7 +593,7 @@ You can test if the "devel" spec is in use with `build.devel?`.
## Compiler selection ## Compiler selection
Sometimes a package fails to build when using a certain compiler. Since recent XCode no longer includes a GCC compiler, we cannot simply force the use of GCC. Instead, the correct way to declare this is the `fails_with` DSL method. A properly constructed `fails_with` block documents the latest compiler build version known to cause compilation to fail, and the cause of the failure. For example: Sometimes a package fails to build when using a certain compiler. Since recent Xcode no longer includes a GCC compiler, we cannot simply force the use of GCC. Instead, the correct way to declare this is the `fails_with` DSL method. A properly constructed `fails_with` block documents the latest compiler build version known to cause compilation to fail, and the cause of the failure. For example:
```ruby ```ruby
fails_with :llvm do fails_with :llvm do

View File

@ -43,7 +43,7 @@ source `brew --repository`/Library/Contributions/brew_bash_completion.sh
``` ```
### ZSH ### Zsh
Run in terminal (may require `sudo`): Run in terminal (may require `sudo`):
```zsh ```zsh

View File

@ -1,7 +1,7 @@
# brew tap # brew tap
The `brew tap` command is powerful, but has a few subtleties worth describing. The `brew tap` command is powerful, but has a few subtleties worth describing.
**tl;dr** `brew tap` allows you to add more Github repos to the list of formulae that `brew` tracks, updates and installs from. When naming tap repos and formulas, however, there are a few gotchas to beware of. **tl;dr** `brew tap` allows you to add more GitHub repos to the list of formulae that `brew` tracks, updates and installs from. When naming tap repos and formulas, however, there are a few gotchas to beware of.
## The command ## The command
@ -27,7 +27,7 @@ telemachus/vim
`brew tap username/repo` employs some shortcuts and has some limitations. `brew tap username/repo` employs some shortcuts and has some limitations.
* On Github, your repository must be named `homebrew-something`. * On GitHub, your repository must be named `homebrew-something`.
The prefix 'homebrew-' is not optional. The prefix 'homebrew-' is not optional.
* When you use `brew tap` on the command line, you can leave out the * When you use `brew tap` on the command line, you can leave out the