typos found by @rilling.

Author: lorenzwalthert

R/initialize.R

@@ -84,10 +84,6 @@ initialize_indent <- function(pd_flat) {
   pd_flat
 }
 
-
-
-
-
 #' @importFrom rlang abort
 #' @describeIn initialize_attributes validates the parse data.
 #' @keywords internal

R/nest.R

@@ -47,7 +47,7 @@ add_cache_block <- function(pd_nested) {
 #' Drop all children of a top level expression that are cached
 #'
 #' Note that we do cache top-level comments. Because package code has a lot of
-#' roxygen comments and each of them is a top level expresion, so checking is
+#' roxygen comments and each of them is a top level expresion, checking is
 #' very expensive.
 #' @param pd A top-level nest.
 #' @details
@@ -62,8 +62,8 @@ add_cache_block <- function(pd_nested) {
 #' [parse_transform_serialize_r_block()], we simply return `text` for the top
 #' level token. For that
 #' reason, the nested parse table can, at the rows where these expressions are
-#' located, be shallow, i.e. it does not have to contain a children, because it
-#' will neighter be transformerd nor serialized anytime. This function drop all
+#' located, be shallow, i.e. it does not have to contain a child, because it
+#' will neither be transformed nor serialized anytime. This function drop all
 #' associated tokens except the top-level token for such expressions, which will
 #' result in large speed improvements in [compute_parse_data_nested()] because
 #' nesting is expensive and will not be done for cached expressions.

R/transform-block.R

@@ -36,7 +36,7 @@ parse_transform_serialize_r_block <- function(pd_nested,
 #' Every expression is an expression itself, Expressions on same line are in
 #' same block.
 #' Multiple expressions can sit on one row, e.g. in line comment and commands
-#' seperated with ";". This creates a problem when processing each expression
+#' separated with ";". This creates a problem when processing each expression
 #' separately because when putting them together, we need complicated handling
 #' of line breaks between them, as it is not apriory clear that there is a line
 #' break separating them. To avoid this, we put top level expressions that sit
@@ -90,7 +90,7 @@ find_blank_lines_to_next_expr <- function(pd_nested) {
 #' @param pd A top level nest.
 find_blank_lines_to_next_block <- function(pd) {
   block_boundary <- pd$block != lag(pd$block, default = 0)
-  # TODO everywhere: block is not ambiguous. use cache block since we also have
+  # TODO everywhere: block is ambiguous. use cache block since we also have
   # block_id and other things in other places
   find_blank_lines_to_next_expr(pd)[block_boundary]
 }

R/utils-cache.R

@@ -15,7 +15,7 @@ hash_standardize <- function(text) {
 
 #' Check if text is cached
 #'
-#' This boilds down to check if the hash exists at the caching dir as a file.
+#' This boils down to check if the hash exists at the caching dir as a file.
 #' @param text,transformers Passed to [cache_make_key()] to generate a key.
 #' @param cache_dir The caching directory relative to the `.Rcache` root to
 #'   look for a cached value.