From 6957539be4d47f27be2315204eb68a1aa5acf44e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20Kn=C3=BCpfer?= Date: Fri, 23 Aug 2024 09:42:50 +0200 Subject: [PATCH] Correct formatting --- episodes/06-rmarkdown.Rmd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/episodes/06-rmarkdown.Rmd b/episodes/06-rmarkdown.Rmd index 0ca3b6a3..179ed59d 100644 --- a/episodes/06-rmarkdown.Rmd +++ b/episodes/06-rmarkdown.Rmd @@ -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 | @@ -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()`.