Merge pull request #1210 from r-lib/rm-nonexistent-vignette-refs

CONTRIBUTING.md

@@ -98,7 +98,7 @@ The source code is organized as follows:
 | token-create.R | Utilities for creating tokens, mostly to insert braces around mutli-line if statements. |
 | token-define.R | Defines which tokens belong to which group. |
 | transform-code.R, transform-files.R | Transformation of code for APIs that manipulate files (e.g. `style_file()`). |
-| ui.R | User interaces. Top-level functions for styling. |
+| ui.R | User interfaces. Top-level functions for styling. |
 | unindent.R | Certain tokens cause unindention, e.g. closing braces. |
 | utils.R | low-level general purpose utilities. |
 | vertical.R | S3 class for pretty printing of styled code. |

DESCRIPTION

@@ -53,6 +53,7 @@ Roxygen: list(markdown = TRUE, roclets = c( "rd", "namespace", "collate",
  warning("Please install r-lib/pkgapi to make sure the file API is kept
  up to date"); NULL}))
 RoxygenNote: 7.3.1
+Language: en-US
 Config/testthat/edition: 3
 Config/testthat/parallel: true
 Collate: 

R/utils-cache.R

@@ -54,7 +54,7 @@ is_cached <- function(text,
 #' a new cache.
 #' * transformers. Cannot easily hash them because two environments won't be
 #' identical even if they contain the same objects (see 'Experiments'). Simple
-#' `as.character(transformers)` will not consider infinitively recursive
+#' `as.character(transformers)` will not consider infinitely recursive
 #' code dependencies.
 #' To fix this, transformers must have names and version number as described
 #' in [create_style_guide()]. Now, the only way to fool the cache invalidation

inst/WORDLIST

@@ -1,10 +1,10 @@
 Addin
 addin
+Addins
 addins
 api
 AppVeyor
 arg
-args
 AST
 aut
 backport
@@ -20,13 +20,11 @@ ci
 cli
 CMD
 codebase
-codecov
 codegrip
 coercible
 coercions
 compat
 config
-Config
 counterpair
 coventions
 cpp
@@ -39,7 +37,6 @@ dependabot
 desc
 devtools
 dir
-dirs
 docsearch
 dont
 dontrun
@@ -67,8 +64,8 @@ gadenbuie
 Gayathri
 getOption
 ggplot
-github
 Github
+github
 gitsum
 gmail
 grkstyle
@@ -79,14 +76,12 @@ https
 icloud
 ifelse
 Indrajeet
-infinitively
 initializer
 inode
 integrations
-interaces
 internal's
-invasiveness
 Invasiveness
+invasiveness
 io
 ixmypi
 JamesIves
@@ -99,6 +94,7 @@ krlmlr
 labelled
 learnr
 LF
+Lifecycle
 lifecycle
 linter
 linters
@@ -148,10 +144,9 @@ PRs
 purrr
 qez
 qmd
-Qmd
 RcppExports
-readme
 README
+readme
 rebased
 reindent
 reindented
@@ -163,25 +158,24 @@ reprex
 revdepcheck
 rlang
 rlang's
-rmarkdown
-Rmarkdown
 RMarkdown
-rmd
+Rmarkdown
+rmarkdown
 Rmd
-rnw
+rmd
 Rnw
+rnw
 roadmap
 Robinlovelace
 roclet
 roclets
 ropensci
 roxgen
-roxygen
 Roxygen
+roxygen
 RoxygenNote
 rplumber
 rprofile
-Rprofile
 rprojroot
 RStudio
 RStudio's
@@ -196,6 +190,8 @@ StackOverflow
 styler
 stylerignore
 stylerignored
+stylers
+Stylers
 sublicense
 summarises
 testthat
@@ -204,6 +200,7 @@ th
 tibble
 tibbles
 tidyr
+Tidyverse
 tidyverse
 todo
 travis
@@ -213,8 +210,8 @@ ui
 uncached
 unexplainable
 unicode
-unindent
 Unindent
+unindent
 unindention
 unlink
 unnest
@@ -235,10 +232,9 @@ xfun
 Xie
 xk
 XN
-yaml
 YAML
+yaml
 yihui
-Yihui
 yl
 YPa
 zm

vignettes/customizing_styler.Rmd

@@ -44,7 +44,7 @@ We note that there are different types of transformer functions. `initialize` in
 tidyverse_style()$space$remove_space_after_opening_paren
 ```
 
-As the name says, this function removes spaces after the opening parenthesis. But how? Its input is a *nest*. Since the visitor will go through all levels of nesting, we just need a function that can be applied to a *nest*, that is, to a parse table at one level of nesting. We can compute the nested parse table and look at one of the levels of nesting that is interesting for us (more on the data structure in the vignettes "Data structures" and "Manipulating the parse table"):
+As the name says, this function removes spaces after the opening parenthesis. But how? Its input is a *nest*. Since the visitor will go through all levels of nesting, we just need a function that can be applied to a *nest*, that is, to a parse table at one level of nesting. We can compute the nested parse table and look at one of the levels of nesting that is interesting for us:
 
 ```{r}
 string_to_format <- "call( 3)"