Minor updates to Days 1, 2

Author: sbreitbart-NOAA

Curriculum/Day_1/day_1.qmd

@@ -46,8 +46,6 @@ Sam Schiano and Sophie Breitbart are contractors with ECS Federal working in sup
 
 -   [Day 1 communal notes doc](https://docs.google.com/document/d/1nVlmmZgp8vCHZKCMHnBm43bf-mtk7pSA1t2FLHEoyZA/edit?tab=t.0#heading=h.lwix6dbx3lr8)
     -   Contains resources (from us and you!) and areas for note-taking
--   [Sample data](https://github.com/nmfs-ost/asar/blob/main/inst/extdata/Report.sso)
-    -   Sample model output data for coding demonstrations
 
 ::: {.callout-note appearance="minimal"}
 Break for questions
@@ -237,10 +235,26 @@ params:
 
 Then, in the body of your report, you can reference this parameter like this:
 
-"The native range of \`params\$species\` spans from..."
+* add a backtick (`)
+* add lowercase 'r'
+* add params + $ + the parameter itself
+* add a backtick (`)
 
-When you knit the document, \`params\$species\` will be replaced with "Petrale sole".
+```{r eval=FALSE}
+`r params$species`
+```
+
+Here is an example. NOTE that this example uses single quotes (') instead of backticks (`), otherwise this page won't render properly. But in your report, use the syntax directly above.
+
+"The native range of 'r params$species' spans from..."
+
+When you knit the document, 'r params$species' will be replaced with "Petrale sole".
 
+::: {.callout-tip}
+To make the species name italicized, add single asterisks (*) around the phrase. For example:
+
+\*'r params$species'* will render as *Petrale sole*.
+:::
 
 ### References and Bibliography
 
@@ -305,6 +319,10 @@ Here are two entries using the examples mentioned above:
 You can edit the glossary by altering, adding, or removing entries in the "report_glossary.tex" file.
 :::
 
+::: {.callout-tip}
+Is there an acronym we've missed that should be included in this national glossary? Make an [issue](https://github.com/nmfs-ost/asar?tab=contributing-ov-file#contributing-bugs) or, even better, a [pull request](https://github.com/nmfs-ost/asar?tab=contributing-ov-file#recommended-workflow-fork--submit-a-pull-request) with your suggestion!
+:::
+
 #### Using acronyms in reports
 
 First, check if the glossary contains your acronym; if it doesn't, you can edit the file and add it yourself.

Curriculum/Day_2/day_2.qmd

@@ -412,9 +412,9 @@ asar::create_template(
 ::: {.callout-important}
 The console will return this question:
 
-> Do you want to keep the current preamble? (Y/N)
+> Update the preamble to match entered arguments? (Y/N)
 
-When you are rerendering your skeleton in a way that edits your preamble (e.g., when you add new model results), your answer should typically be NO (n).
+When you are rerendering your skeleton in a way that edits your preamble (e.g., when you add new model results), your answer should typically be YES (y).
 
 Just be aware that these changes will, in fact, change your current preamble and overwrite any edits you made to that file.
 :::