Work on spelling stuff

Author: jennybc

NEWS.md

@@ -27,7 +27,7 @@ usethis has a more sophisticated understanding of the default branch and gains s
 ## Other
 
 * `use_github_file()` is a new function related to `use_template()`, which grabs
-  the contents of an arbitrary file on GitHub, with support for targetting a
+  the contents of an arbitrary file on GitHub, with support for targeting a
   specific branch, tag, or commit and for following symlinks (#1407). It is now
   used by `use_github_action()` and friends.
 

inst/WORDLIST

@@ -15,6 +15,7 @@ Depsy
 DockerHub
 DropBox
 GHA
+GHE
 Gert
 Gert's
 Git's
@@ -33,7 +34,6 @@ Lifecycle
 LinkingTo
 Makefile
 ORCID
-PAT's
 PATs
 PRs
 README
@@ -57,7 +57,6 @@ Templated
 Tidyverse
 UI
 Ushey's
-VM
 Xcode
 YAML
 addin
@@ -90,7 +89,6 @@ discoverable
 else's
 emacs
 eval
-favicons
 favour
 fiascos
 filenaming
@@ -122,8 +120,8 @@ labelling
 learnr
 libgit
 lifecycle
-linux
 macOS
+macbook
 magrittr
 magrittr's
 md
@@ -148,7 +146,6 @@ rcmdcheck
 rebase
 reconfigures
 redirections
-renviron
 repo
 repo's
 repos
@@ -170,10 +167,12 @@ sitrep
 src
 styler
 symlink
+symlinks
 templated
 templating
 testthat
 tibble
+tidymodels
 tidyverse
 todo
 travis
@@ -184,6 +183,9 @@ unpushed
 useR
 usethis's
 ver
+vm
 withr
+www
+xyz
 xz
 yaml

vignettes/articles/git-credentials.Rmd

@@ -149,7 +149,7 @@ Copy the PAT to the clipboard, anticipating what we'll do next: trigger a prompt
 
 Sidebar about storing your PAT: If you use a password management app, such as 1Password or LastPass (highly recommended!), you might want to add this PAT (and its *Note*) to the entry for GitHub.
 Storing your PAT in the Git credential store is a semi-persistent convenience, sort of like a browser cache or "remember me" on a website, but it's quite possible you will need to re-enter your PAT in the future.
-You could decide to embrace the impermanance of your PAT and, if it is somehow removed from the store, you'll just re-generate a new PAT and re-enter it.
+You could decide to embrace the impermanence of your PAT and, if it is somehow removed from the store, you'll just re-generate a new PAT and re-enter it.
 If you accept the default 30-day expiration period, this is a workflow you'll be using often anyway.
 But if you create long-lasting tokens or want to play around with the functions for setting or clearing your Git credentials, it can be handy to have your own record of your PAT in a secure place, like 1Password or LastPass.
 
@@ -289,7 +289,7 @@ Once they retrieve a PAT from the store, they temporarily cache it in an environ
 This allows a discovered PAT to be reused, potentially by multiple packages, repeatedly over the course of an R session.
 
 Using `.Renviron` as your primary PAT store is less secure and, if you can, it is safer to keep your PAT in the Git credential store and let packages that need it to discover it there upon first need.
-Linux users may still need to use the `.Renviron` method, since they don't have easy access to OS-managed stores like macOS's Keychain or Windows Credential Manager.
+Linux users may still need to use the `.Renviron` method, since they don't have easy access to OS-managed stores like the macOS Keychain or Windows Credential Manager.
 
 If you still need to use `.Renviron` method, `usethis::edit_r_environ()` opens that file for editing.
 
@@ -340,7 +340,7 @@ Do NOT define `GITHUB_PAT` in `.Renviron`.
 If you want to keep using remotes, instead of pak, you could just rely on the built-in credential.
 This will suffice if rate-limiting is the only concern, but obviously will not provide access to private repositories.
 
-If you really want to use remotes, with your own PAT, you can "tickle" gitcreds, via `gitcreds::gitcreds_get()`, to get it to load your PAT from the store into the `GITHUB_PAT` env var, where remotes will happily find it.
+If you really want to use remotes, with your own PAT, you can "tickle" gitcreds, via `gitcreds::gitcreds_get()`, to get it to load your PAT from the store into the `GITHUB_PAT` environment variable, where remotes will happily find it.
 This could be done interactively as needed, written into individual scripts, or
 even executed in a startup file.
 This still avoids defining `GITHUB_PAT` in `.Renviron`.