diff --git a/R/colwise-mutate.R b/R/colwise-mutate.R index aa99c3d4c4..89bda18f9d 100644 --- a/R/colwise-mutate.R +++ b/R/colwise-mutate.R @@ -75,7 +75,7 @@ #' #' Name collisions in the new columns are disambiguated using a unique suffix. #' -#' @section Life cycle: +#' @section Lifecycle: #' #' The functions are maturing, because the naming scheme and the #' disambiguation algorithm are subject to change in dplyr 0.9.0. @@ -196,7 +196,7 @@ summarize_at <- summarise_at #' `transmute_if()`. #' #' @inheritSection summarise_all Naming -#' @inheritSection summarise_all Life cycle +#' @inheritSection summarise_all Lifecycle #' #' @examples #' iris <- as_tibble(iris) diff --git a/R/group-nest.R b/R/group-nest.R index 24f01f43c5..7962ae2a32 100644 --- a/R/group-nest.R +++ b/R/group-nest.R @@ -10,7 +10,7 @@ group_nest_impl <- function(.tbl, .key, keep = FALSE){ #' #' Nest a tibble using a grouping specification #' -#' @section Life cycle: +#' @section Lifecycle: #' `group_nest()` is not stable because [`tidyr::nest(.by =)`][tidyr::nest()] #' provides very similar behavior. It may be deprecated in the future. #' diff --git a/R/group-split.R b/R/group-split.R index a3cf93d2e3..2212d86d8a 100644 --- a/R/group-split.R +++ b/R/group-split.R @@ -17,7 +17,7 @@ #' is generally not very useful as you want have easy access to the group #' metadata. #' -#' @section Life cycle: +#' @section Lifecycle: #' `group_split()` is not stable because you can achieve very similar results by #' manipulating the nested column returned from #' [`tidyr::nest(.by =)`][tidyr::nest()]. That also retains the group keys all diff --git a/R/nest-by.R b/R/nest-by.R index 4710ffb1b8..6b2abc531d 100644 --- a/R/nest-by.R +++ b/R/nest-by.R @@ -30,7 +30,7 @@ #' reframe(data) #' ``` #' -#' @section Life cycle: +#' @section Lifecycle: #' `nest_by()` is not stable because [`tidyr::nest(.by =)`][tidyr::nest()] #' provides very similar behavior. It may be deprecated in the future. #' diff --git a/man/group_nest.Rd b/man/group_nest.Rd index 308aac9003..389271bacc 100644 --- a/man/group_nest.Rd +++ b/man/group_nest.Rd @@ -25,7 +25,7 @@ with matching rows of the remaining columns. Nest a tibble using a grouping specification } -\section{Life cycle}{ +\section{Lifecycle}{ \code{group_nest()} is not stable because \code{\link[tidyr:nest]{tidyr::nest(.by =)}} provides very similar behavior. It may be deprecated in the future. diff --git a/man/group_split.Rd b/man/group_split.Rd index 6f77dafc72..41770c297a 100644 --- a/man/group_split.Rd +++ b/man/group_split.Rd @@ -38,7 +38,7 @@ You can pass \code{...} to group and split an ungrouped data frame, but this is generally not very useful as you want have easy access to the group metadata. } -\section{Life cycle}{ +\section{Lifecycle}{ \code{group_split()} is not stable because you can achieve very similar results by manipulating the nested column returned from diff --git a/man/mutate_all.Rd b/man/mutate_all.Rd index 2ebafc5987..2ecfb2322f 100644 --- a/man/mutate_all.Rd +++ b/man/mutate_all.Rd @@ -115,7 +115,7 @@ If a variable in \code{.vars} is named, a new column by that name will be create Name collisions in the new columns are disambiguated using a unique suffix. } -\section{Life cycle}{ +\section{Lifecycle}{ The functions are maturing, because the naming scheme and the diff --git a/man/nest_by.Rd b/man/nest_by.Rd index 4361dc56dd..bc9df30ffe 100644 --- a/man/nest_by.Rd +++ b/man/nest_by.Rd @@ -63,7 +63,7 @@ If you want to unnest a nested data frame, you can either use reframe(data) }\if{html}{\out{}} } -\section{Life cycle}{ +\section{Lifecycle}{ \code{nest_by()} is not stable because \code{\link[tidyr:nest]{tidyr::nest(.by =)}} provides very similar behavior. It may be deprecated in the future. diff --git a/man/summarise_all.Rd b/man/summarise_all.Rd index e20d71035c..37b7f01861 100644 --- a/man/summarise_all.Rd +++ b/man/summarise_all.Rd @@ -117,7 +117,7 @@ If a variable in \code{.vars} is named, a new column by that name will be create Name collisions in the new columns are disambiguated using a unique suffix. } -\section{Life cycle}{ +\section{Lifecycle}{ The functions are maturing, because the naming scheme and the