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

Fixed typos (#1315) 

- by time -> by the time
- last sentence of the chapter refers to next chapter as focusing on getting help, which seems to be an error due to the reordering to chapters.
This commit is contained in:
Jonathan Kitt 2023-02-28 14:36:29 +01:00 committed by GitHub
parent 89f587b75e
commit bf07203845
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
EDA.qmd
View File

@ -279,7 +279,7 @@ If you've encountered unusual values in your dataset, and simply want to move on
```
We don't recommend this option because just because one measurement is invalid, doesn't mean all the measurements are.
Additionally, if you have low quality data, by time that you've applied this approach to every variable you might find that you don't have any data left!
Additionally, if you have low quality data, by the time that you've applied this approach to every variable you might find that you don't have any data left!
2. Instead, we recommend replacing the unusual values with missing values.
The easiest way to do this is to use `mutate()` to replace the variable with a modified copy.
@ -766,4 +766,4 @@ In this chapter you've learned a variety of tools to help you understand the var
You've seen technique that work with a single variable at a time and with a pair of variables.
This might seem painful restrictive if you have tens or hundreds of variables in your data, but they're foundation upon which all other techniques are built.
In the next chapter, we'll tackle our final piece of workflow advice: how to get help when you're stuck.
In the next chapter, we'll focus on the tools we can use to communicate our results.