From dc95230a6d39c5437791d07a0a85f7385f2e31c7 Mon Sep 17 00:00:00 2001 From: Mitsuo Shiota <48662507+mitsuoxv@users.noreply.github.com> Date: Thu, 25 May 2023 03:17:55 +0900 Subject: [PATCH] Fix/iteration typos (#1491) * a typo * a typo * a typo * Update iteration.qmd --------- Co-authored-by: Mine Cetinkaya-Rundel --- iteration.qmd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/iteration.qmd b/iteration.qmd index 8e1f3ad..5316cdb 100644 --- a/iteration.qmd +++ b/iteration.qmd @@ -220,7 +220,7 @@ df_miss |> ) ``` -If you look carefully, you might intuit that the columns are named using using a glue specification (@sec-glue) like `{.col}_{.fn}` where `.col` is the name of the original column and `.fn` is the name of the function. +If you look carefully, you might intuit that the columns are named using a glue specification (@sec-glue) like `{.col}_{.fn}` where `.col` is the name of the original column and `.fn` is the name of the function. That's not a coincidence! As you'll learn in the next section, you can use `.names` argument to supply your own glue spec. @@ -785,7 +785,7 @@ data <- files |> list_rbind() This works particularly well here because `list_rbind()`, like many tidyverse functions, automatically ignores `NULL`s. -Now you have all the data that can be read easily, and it's time to tackle the hard part of figuring out why some files failed to load and what do to about it. +Now you have all the data that can be read easily, and it's time to tackle the hard part of figuring out why some files failed to load and what to do about it. Start by getting the paths that failed: ```{r}