Remove line break + visual editor moved chunk
This commit is contained in:
parent
2c04b84d46
commit
dc2e531499
|
@ -231,8 +231,10 @@ The code in the book looks like this:
|
||||||
|
|
||||||
If you run the same code in your local console, it will look like this:
|
If you run the same code in your local console, it will look like this:
|
||||||
|
|
||||||
> 1 + 2
|
```
|
||||||
[1] 3
|
> 1 + 2
|
||||||
|
[1] 3
|
||||||
|
```
|
||||||
|
|
||||||
There are two main differences.
|
There are two main differences.
|
||||||
In your console, you type after the `>`, called the **prompt**; we don't show the prompt in the book.
|
In your console, you type after the `>`, called the **prompt**; we don't show the prompt in the book.
|
||||||
|
@ -245,8 +247,7 @@ Throughout the book, we use a consistent set of conventions to refer to code:
|
||||||
|
|
||||||
- Other R objects (such as data or function arguments) are in a code font, without parentheses, like `flights` or `x`.
|
- Other R objects (such as data or function arguments) are in a code font, without parentheses, like `flights` or `x`.
|
||||||
|
|
||||||
- Sometimes, to make it clear which package an object comes from, we'll use the package name followed by two colons, like `dplyr::mutate()` or\
|
- Sometimes, to make it clear which package an object comes from, we'll use the package name followed by two colons, like `dplyr::mutate()` or `nycflights13::flights`.
|
||||||
`nycflights13::flights`.
|
|
||||||
This is also valid R code.
|
This is also valid R code.
|
||||||
|
|
||||||
## Acknowledgments
|
## Acknowledgments
|
||||||
|
|
Loading…
Reference in New Issue