diff --git a/doc/reporting_bugs/curl_error_fix_curlrc.md b/doc/reporting_bugs/curl_error_fix_curlrc.md index cb74139faf..889643a1af 100644 --- a/doc/reporting_bugs/curl_error_fix_curlrc.md +++ b/doc/reporting_bugs/curl_error_fix_curlrc.md @@ -1,5 +1,5 @@ [Go back](a_cask_fails_to_install.md#curl-error) -First, lets tackle a common problem: do you have a `.curlrc` file? Those are a frequent cause of issues of this nature. Before anything else, remove that file and try again. If it now works, do not open an issue. Incompatible `.curlrc` configurations must be fixed on your side. +First, let's tackle a common problem: do you have a `.curlrc` file? Those are a frequent cause of issues of this nature. Before anything else, remove that file and try again. If it now works, do not open an issue. Incompatible `.curlrc` configurations must be fixed on your side. -If, however, you do not have a `.curlrc` or removing it did not work, lets [continue our diagnose](curl_error_fix_vendor.md). +If, however, you do not have a `.curlrc` or removing it did not work, let's [continue our diagnosis](curl_error_fix_vendor.md). diff --git a/doc/reporting_bugs/curl_error_fix_outdated.md b/doc/reporting_bugs/curl_error_fix_outdated.md index a496e5c395..9c2f5b6efd 100644 --- a/doc/reporting_bugs/curl_error_fix_outdated.md +++ b/doc/reporting_bugs/curl_error_fix_outdated.md @@ -1,6 +1,6 @@ [Go back](curl_error_fix_vendor.md) -Since the download started, it likely means the cask is outdated. Lets fix it: +Since the download started, it likely means the cask is outdated. Let's fix it: 1. Look around the app’s website and find out what the latest version is. It will likely be expressed in the URL used to download it. 2. Take a look at the cask’s version (`brew cask _stanza version {{cask_name}}`) and verify it is indeed outdated. diff --git a/doc/reporting_bugs/curl_error_fix_vendor.md b/doc/reporting_bugs/curl_error_fix_vendor.md index bcb785ba79..281e455421 100644 --- a/doc/reporting_bugs/curl_error_fix_vendor.md +++ b/doc/reporting_bugs/curl_error_fix_vendor.md @@ -1,8 +1,8 @@ [Go back](curl_error_fix_curlrc) -Lets now see if the issue is upstream: +Let's now see if the issue is upstream: -1. Got to the vendor’s website (`brew cask home {{cask_name}}`). +1. Go to the vendor’s website (`brew cask home {{cask_name}}`). 2. Find the download link for the app and click on it. Does it download? [Yes](curl_error_fix_outdated.md) | [No](curl_error_fix_wont_fix.md) | [There is nothing to download](curl_error_fix_no_download.md) diff --git a/doc/reporting_bugs/sha256_mismatch_error_fix_icomplete.md b/doc/reporting_bugs/sha256_mismatch_error_fix_icomplete.md index 7da4883340..361f019649 100644 --- a/doc/reporting_bugs/sha256_mismatch_error_fix_icomplete.md +++ b/doc/reporting_bugs/sha256_mismatch_error_fix_icomplete.md @@ -1,5 +1,5 @@ [Go back](a_cask_fails_to_install.md#sha256-mismatch-error) -First, lets see if the problem was with your download. Delete the downloaded file (its location will be pointed out right under the `Actual` shasum line) and try again. +First, let's see if the problem was with your download. Delete the downloaded file (its location will be pointed out right under the `Actual` shasum line) and try again. If the problem persists, [the cask must be outdated](sha256_mismatch_error_fix_outdated.md). diff --git a/doc/reporting_bugs/sha256_mismatch_error_fix_outdated.md b/doc/reporting_bugs/sha256_mismatch_error_fix_outdated.md index 90f3df9071..7c6f65c6a5 100644 --- a/doc/reporting_bugs/sha256_mismatch_error_fix_outdated.md +++ b/doc/reporting_bugs/sha256_mismatch_error_fix_outdated.md @@ -1,8 +1,8 @@ [Go back](sha256_mismatch_error_fix_icomplete.md) -Lets bring the cask up to date. It’ll likely need a new version, but it’s possible the version has remained the same (happens occasionally when the vendor updates the app in place). +Let's bring the cask up to date. It’ll likely need a new version, but it’s possible the version has remained the same (happens occasionally when the vendor updates the app in place). -1. Got to the vendor’s website (`brew cask home {{cask_name}}`). +1. Go to the vendor’s website (`brew cask home {{cask_name}}`). * Alternatively, if it has an `appcast`, read that (`curl "$(brew cask _stanza appcast {{cask_name}})"`). 2. Find out what the latest version is. It will likely be expressed in the URL used to download it. 3. Take a look at the cask’s version (`brew cask _stanza version {{cask_name}}`) and verify it is indeed outdated. diff --git a/doc/reporting_bugs/source_is_not_there_fix.md b/doc/reporting_bugs/source_is_not_there_fix.md index 324912bdfb..cf459e0fcc 100644 --- a/doc/reporting_bugs/source_is_not_there_fix.md +++ b/doc/reporting_bugs/source_is_not_there_fix.md @@ -11,7 +11,7 @@ Fixing this error is typically easy, and requires only a bit of time on your par └─ README.md ``` -Now, lets look at the cask (`brew cask cat {{cask_name}}`: +Now, let's look at the cask (`brew cask cat {{cask_name}}`: ``` (…) @@ -21,7 +21,7 @@ app 'SomeApp.app' The cask was expecting `SomeApp.app` to be in the top directory of the archive (see how it says simply `SomeApp.app`) but the developer changed it to inside a `Files` directory. All we have to do is update that line of the cask to follow the new structure: `app 'Files/SomeApp.app'`. -Note that occasionally the app’s name changes completely (from `SomeApp.app` to `OtherApp.app`, lets say). In these instances, the filename of the cask itself, as well as its token, must also change. Consult the [`token reference`](https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/token_reference.md) for complete instructions on the new name. +Note that occasionally the app’s name changes completely (from `SomeApp.app` to `OtherApp.app`, let's say). In these instances, the filename of the cask itself, as well as its token, must also change. Consult the [`token reference`](https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/token_reference.md) for complete instructions on the new name. Follow the instructions to [submit a fix](../../CONTRIBUTING.md#updating-a-cask), and make the change to the cask. If using `cask-repair`, you may give it the `--edit-cask` flag when calling it on the command-line to step right into editing it. If you’re having trouble, open an issue [with this template][issue_source_not_there_and_cannot_find_it] explaining your steps so far and why you’re having trouble submitting the update.