course/r4ds
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix minor typos (#1083)

Browse Source
This commit is contained in:
Betul Turkoglu
2022-09-02 14:35:55 +03:00
committed by GitHub
parent 53146f68d1
commit b676118cbd
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
EDA.qmd
View File

@@ -788,7 +788,7 @@ ggplot(data = smaller, mapping = aes(x = carat, y = price)) +
What do you need to consider when using `cut_width()` vs `cut_number()`?
How does that impact a visualization of the 2d distribution of `carat` and `price`?
2. Visualize the distribution of carat, partitioned by price.
2. Visualize the distribution of `carat`, partitioned by `price`.
3. How does the price distribution of very large diamonds compare to small diamonds?
Is it as you expect, or does it surprise you?

4
workflow-pipes.qmd
View File

@@ -17,7 +17,7 @@ You'll need to make one change to your RStudio options to use `|>` instead of `%
#| label: fig-pipe-options
#| echo: false
#| fig-cap: >
#| To insert `|>`, make sure the "Use native pipe" option is checked.
#| To insert `|>`, make sure the "Use native pipe operator" option is checked.
#| fig-alt: >
#| Screenshot showing the "Use native pipe operator" option which can
#| be found on the "Editing" panel of the "Code" options.
@@ -42,7 +42,7 @@ flights |>
)
```
Even though this pipe has four steps, it's easy to skim because the verbs come at the start of each line: start with the flights data, then filter, then group, then summarize.
Even though this pipe has four steps, it's easy to skim because the verbs come at the start of each line: start with the `flights` data, then filter, then group, then summarize.
What would happen if we didn't have the pipe?
We could nest each function call inside the previous call: