Skip to content

Commit

Permalink
Fixes typos in workflow-projects.Rmd
Browse files Browse the repository at this point in the history
  • Loading branch information
garrettgman authored Oct 31, 2016
1 parent 81dc7a7 commit ca2e1ab
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions workflow-projects.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ getwd()
#> [1] "/Users/hadley/Documents/r4ds/r4ds"
```

As a beginning R user, it's OK let your home directory, documents directory, or any other weird directory on your computer be R's working directory. But you're six chapters into this book, and you're no longer a rank beginner. Very soon now you should evolve to organising your analytical projects into directories and, when working on a project, setting R's working directory to the associated directory.
As a beginning R user, it's OK to let your home directory, documents directory, or any other weird directory on your computer be R's working directory. But you're six chapters into this book, and you're no longer a rank beginner. Very soon now you should evolve to organising your analytical projects into directories and, when working on a project, setting R's working directory to the associated directory.

__I do not recommend it__, but you can also set the working directory from within R:

Expand All @@ -70,7 +70,7 @@ Paths and directories are a little complicated because there are two basic style
letter (e.g. `C:`) or two backslashes (e.g. `\\servername`) and in
Mac/Linux they start with a slash "/" (e.g. `/users/hadley`). You should
__never__ use absolute paths in your scripts, because they hinder sharing:
noone else will have exactly the same directory configuration as you.
no one else will have exactly the same directory configuration as you.

1. The last minor difference is the place that `~` points to. `~` is a
convenient shortcut to your home directory. Windows doesn't really have
Expand Down

0 comments on commit ca2e1ab

Please sign in to comment.