Skip to content

Commit

Permalink
Merge pull request #518 from cknuepfer/patch-2
Browse files Browse the repository at this point in the history
Correct formatting
  • Loading branch information
juanfung committed Aug 23, 2024
2 parents cbeb842 + 6957539 commit 97188f0
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions episodes/06-rmarkdown.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -322,7 +322,7 @@ Many different R packages can be used to generate tables. Some of the more commo
We mentioned using `include = FALSE` in a code chunk to prevent the code and
output from printing in the knitted document. There are additional options
available to customise how the code-chunks are presented in the output document.
The options are entered in the code chunk after `chunk-name`and separated by
The options are entered in the code chunk after `chunk-name` and separated by
commas, e.g. `{r chunk-name, eval = FALSE, echo = TRUE}`.

| Option | Options | Output |
Expand Down Expand Up @@ -377,8 +377,8 @@ Now we will use some in-line R code to present some descriptive statistics.
To use in-line R-code, we use the same backticks that we used in the Markdown
section, with an `r` to specify that we are generating R-code. The difference
between in-line code and a code chunk is the number of backticks. In-line R code
uses one backtick (`r`), whereas code chunks use three backticks
(``` r ```).
uses one backtick (`` `r` ``), whereas code chunks use three backticks
(`` ```r``` ``).

For example, today's date is ``` ``r "r Sys.Date()"`` ```, will be rendered as:
today's date is `r Sys.Date()`.
Expand Down

0 comments on commit 97188f0

Please sign in to comment.