diff --git a/02-using_quarto-web.qmd b/02-using_quarto-web.qmd index 6fc95c7..1187c0e 100644 --- a/02-using_quarto-web.qmd +++ b/02-using_quarto-web.qmd @@ -347,7 +347,7 @@ In order to be successful in these chapters, you must do the following: 2. **Copy and paste thoughtfully!** - Not every piece of code from the early part of the chapter will necessarily apply to the later exercises. And the code that does apply will need to be modified (sometimes quite heavily) to be able to run new analyses. Your job is to understand how the code works so that you can make changes to it without breaking things. If you don't understand a piece of code, don't copy and paste it until you've read and re-read the earlier exposition that explains how the code works. -One final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don't actually work as plain text in an Quarto. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that. +One final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don't actually work as plain text in a Quarto document. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that. ## Conclusion @@ -358,26 +358,26 @@ That's it! There wasn't too much you were asked to do for this assignment that w ### Preparing and submitting your assignment -If you look in your project folder, you should see three files: +If you look in your project folder, you should see (at least) three files: ``` [a file with a .Rproj extension, either project.Rproj or intro_stats.Rproj] -02-using_quarto.html 02-using_quarto.qmd +02-using_quarto.html ``` The first file (with extension `.Rproj`) you were instructed never to touch. -The next file has extension `.html`. That is the pretty output file generated when you hit the "Render" button. This is the "final product" of your work. +The next file has extension `.qmd`. This is your Quarto file. It's the file you're looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run. -Finally, you have a file with extension `.qmd`. This is your Quarto file. It's the file you're looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run. +Finally, you have a file with extension `.html`. This is the pretty output file generated when you hit the "Render" button. This is the "final product" of your work. (If you happen to see other files or folders in your project folder, you should ignore those and not mess with them.) There are several steps that you should follow at the end of each of every chapter. 1. From the "Run" menu, select "Restart R and Run All Chunks". -2. Deal with any code errors that crop up. Repeat steps 1–-2 until there are no more code errors. +2. Deal with any code errors that crop up. Repeat steps 1--2 until there are no more code errors. 3. Spell check your document by clicking the icon with "ABC" and a check mark. 4. Hit the "Render" button one last time to generate the final draft of the HTML file. (If there are errors here, you may need to go back and fix broken inline code or other markdown issues.) 5. Proofread the HTML file carefully. If there are errors, go back and fix them, then repeat steps 1--5 again. diff --git a/chapter_downloads/02-using_quarto.qmd b/chapter_downloads/02-using_quarto.qmd index d26c1ca..72ddee4 100644 --- a/chapter_downloads/02-using_quarto.qmd +++ b/chapter_downloads/02-using_quarto.qmd @@ -357,7 +357,7 @@ In order to be successful in these chapters, you must do the following: 2. **Copy and paste thoughtfully!** - Not every piece of code from the early part of the chapter will necessarily apply to the later exercises. And the code that does apply will need to be modified (sometimes quite heavily) to be able to run new analyses. Your job is to understand how the code works so that you can make changes to it without breaking things. If you don't understand a piece of code, don't copy and paste it until you've read and re-read the earlier exposition that explains how the code works. -One final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don't actually work as plain text in an Quarto. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that. +One final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don't actually work as plain text in a Quarto document. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that. ## Conclusion @@ -368,26 +368,26 @@ That's it! There wasn't too much you were asked to do for this assignment that w ### Preparing and submitting your assignment -If you look in your project folder, you should see three files: +If you look in your project folder, you should see (at least) three files: ``` [a file with a .Rproj extension, either project.Rproj or intro_stats.Rproj] -02-using_quarto.html 02-using_quarto.qmd +02-using_quarto.html ``` The first file (with extension `.Rproj`) you were instructed never to touch. -The next file has extension `.html`. That is the pretty output file generated when you hit the "Render" button. This is the "final product" of your work. +The next file has extension `.qmd`. This is your Quarto file. It's the file you're looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run. -Finally, you have a file with extension `.qmd`. This is your Quarto file. It's the file you're looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run. +Finally, you have a file with extension `.html`. This is the pretty output file generated when you hit the "Render" button. This is the "final product" of your work. (If you happen to see other files or folders in your project folder, you should ignore those and not mess with them.) There are several steps that you should follow at the end of each of every chapter. 1. From the "Run" menu, select "Restart R and Run All Chunks". -2. Deal with any code errors that crop up. Repeat steps 1–-2 until there are no more code errors. +2. Deal with any code errors that crop up. Repeat steps 1--2 until there are no more code errors. 3. Spell check your document by clicking the icon with "ABC" and a check mark. 4. Hit the "Render" button one last time to generate the final draft of the HTML file. (If there are errors here, you may need to go back and fix broken inline code or other markdown issues.) 5. Proofread the HTML file carefully. If there are errors, go back and fix them, then repeat steps 1--5 again. diff --git a/docs/02-using_quarto-web.html b/docs/02-using_quarto-web.html index 17673ac..e8ac30b 100644 --- a/docs/02-using_quarto-web.html +++ b/docs/02-using_quarto-web.html @@ -577,25 +577,25 @@

  • Not every piece of code from the early part of the chapter will necessarily apply to the later exercises. And the code that does apply will need to be modified (sometimes quite heavily) to be able to run new analyses. Your job is to understand how the code works so that you can make changes to it without breaking things. If you don’t understand a piece of code, don’t copy and paste it until you’ve read and re-read the earlier exposition that explains how the code works.
    • -

    One final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don’t actually work as plain text in an Quarto. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that.

    +

    One final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don’t actually work as plain text in a Quarto document. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that.

    2.13 Conclusion

    That’s it! There wasn’t too much you were asked to do for this assignment that will actually show up in the HTML output. (Make sure you did do the three things that were asked of you, however: one was adding your name and the date to the YAML header, one was typing something in the blue answer box, and the last was to make a section header appear properly.) As you gain confidence and as we move into more serious stats material, you will be asked to do a lot more.

    2.13.1 Preparing and submitting your assignment

    -

    If you look in your project folder, you should see three files:

    +

    If you look in your project folder, you should see (at least) three files:

    [a file with a .Rproj extension, either project.Rproj or intro_stats.Rproj]
-02-using_quarto.html
-02-using_quarto.qmd
    +02-using_quarto.qmd +02-using_quarto.html

    The first file (with extension .Rproj) you were instructed never to touch.

    -

    The next file has extension .html. That is the pretty output file generated when you hit the “Render” button. This is the “final product” of your work.

    -

    Finally, you have a file with extension .qmd. This is your Quarto file. It’s the file you’re looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run.

    +

    The next file has extension .qmd. This is your Quarto file. It’s the file you’re looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run.

    +

    Finally, you have a file with extension .html. This is the pretty output file generated when you hit the “Render” button. This is the “final product” of your work.

    (If you happen to see other files or folders in your project folder, you should ignore those and not mess with them.)

    There are several steps that you should follow at the end of each of every chapter.

    1. From the “Run” menu, select “Restart R and Run All Chunks”.
      2. -
    2. Deal with any code errors that crop up. Repeat steps 1–-2 until there are no more code errors.
      3. +
    3. Deal with any code errors that crop up. Repeat steps 1–2 until there are no more code errors.
    4. Spell check your document by clicking the icon with “ABC” and a check mark.
    5. Hit the “Render” button one last time to generate the final draft of the HTML file. (If there are errors here, you may need to go back and fix broken inline code or other markdown issues.)
    6. Proofread the HTML file carefully. If there are errors, go back and fix them, then repeat steps 1–5 again.
      7. diff --git a/docs/chapter_downloads/02-using_quarto.qmd b/docs/chapter_downloads/02-using_quarto.qmd index d26c1ca..72ddee4 100644 --- a/docs/chapter_downloads/02-using_quarto.qmd +++ b/docs/chapter_downloads/02-using_quarto.qmd @@ -357,7 +357,7 @@ In order to be successful in these chapters, you must do the following: 2. **Copy and paste thoughtfully!** - Not every piece of code from the early part of the chapter will necessarily apply to the later exercises. And the code that does apply will need to be modified (sometimes quite heavily) to be able to run new analyses. Your job is to understand how the code works so that you can make changes to it without breaking things. If you don't understand a piece of code, don't copy and paste it until you've read and re-read the earlier exposition that explains how the code works. -One final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don't actually work as plain text in an Quarto. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that. +One final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don't actually work as plain text in a Quarto document. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that. ## Conclusion @@ -368,26 +368,26 @@ That's it! There wasn't too much you were asked to do for this assignment that w ### Preparing and submitting your assignment -If you look in your project folder, you should see three files: +If you look in your project folder, you should see (at least) three files: ``` [a file with a .Rproj extension, either project.Rproj or intro_stats.Rproj] -02-using_quarto.html 02-using_quarto.qmd +02-using_quarto.html ``` The first file (with extension `.Rproj`) you were instructed never to touch. -The next file has extension `.html`. That is the pretty output file generated when you hit the "Render" button. This is the "final product" of your work. +The next file has extension `.qmd`. This is your Quarto file. It's the file you're looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run. -Finally, you have a file with extension `.qmd`. This is your Quarto file. It's the file you're looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run. +Finally, you have a file with extension `.html`. This is the pretty output file generated when you hit the "Render" button. This is the "final product" of your work. (If you happen to see other files or folders in your project folder, you should ignore those and not mess with them.) There are several steps that you should follow at the end of each of every chapter. 1. From the "Run" menu, select "Restart R and Run All Chunks". -2. Deal with any code errors that crop up. Repeat steps 1–-2 until there are no more code errors. +2. Deal with any code errors that crop up. Repeat steps 1--2 until there are no more code errors. 3. Spell check your document by clicking the icon with "ABC" and a check mark. 4. Hit the "Render" button one last time to generate the final draft of the HTML file. (If there are errors here, you may need to go back and fix broken inline code or other markdown issues.) 5. Proofread the HTML file carefully. If there are errors, go back and fix them, then repeat steps 1--5 again. diff --git a/docs/search.json b/docs/search.json index 0c38afa..e224b25 100644 --- a/docs/search.json +++ b/docs/search.json @@ -304,7 +304,7 @@ "href": "02-using_quarto-web.html#copying-and-pasting", "title": "2  Using Quarto", "section": "2.12 Copying and pasting", - "text": "2.12 Copying and pasting\nIn future chapters, you will be shown how to run statistical analyses using R. Each chapter will give extensive explanations of the statistical concepts and demonstrations of the necessary R code. Afterwards, there will be one or more exercises that ask you to apply your new-found knowledge to run similar analyses on your own with different data.\nThe idea is that you should be able to copy and paste the R code from the previously worked examples. But you must be thoughtful about how you do this. The code cannot just be copied and pasted blindly. It must be modified so that it applies to the exercises with new data. This requires that you understand what the code is doing. You cannot effectively modify the code if you don’t know which parts to modify.\nThere will also be exercises in which you are asked to provide your own explanations and interpretations of your analyses. These should not be copied and pasted from any previous work. These exercises are designed to help you understand the statistical concepts, so they must be in your own words, using your own understanding.\nIn order to be successful in these chapters, you must do the following:\n\nRead every part of the chapter carefully!\n\n\nIt will be tempting to skim over the paragraphs quickly and just jump from code chunk to code chunk. This will be highly detrimental to your ability to gain the necessary understanding—not just to complete the chapter, but to succeed in statistics overall.\n\n\nCopy and paste thoughtfully!\n\n\nNot every piece of code from the early part of the chapter will necessarily apply to the later exercises. And the code that does apply will need to be modified (sometimes quite heavily) to be able to run new analyses. Your job is to understand how the code works so that you can make changes to it without breaking things. If you don’t understand a piece of code, don’t copy and paste it until you’ve read and re-read the earlier exposition that explains how the code works.\n\nOne final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don’t actually work as plain text in an Quarto. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that.", + "text": "2.12 Copying and pasting\nIn future chapters, you will be shown how to run statistical analyses using R. Each chapter will give extensive explanations of the statistical concepts and demonstrations of the necessary R code. Afterwards, there will be one or more exercises that ask you to apply your new-found knowledge to run similar analyses on your own with different data.\nThe idea is that you should be able to copy and paste the R code from the previously worked examples. But you must be thoughtful about how you do this. The code cannot just be copied and pasted blindly. It must be modified so that it applies to the exercises with new data. This requires that you understand what the code is doing. You cannot effectively modify the code if you don’t know which parts to modify.\nThere will also be exercises in which you are asked to provide your own explanations and interpretations of your analyses. These should not be copied and pasted from any previous work. These exercises are designed to help you understand the statistical concepts, so they must be in your own words, using your own understanding.\nIn order to be successful in these chapters, you must do the following:\n\nRead every part of the chapter carefully!\n\n\nIt will be tempting to skim over the paragraphs quickly and just jump from code chunk to code chunk. This will be highly detrimental to your ability to gain the necessary understanding—not just to complete the chapter, but to succeed in statistics overall.\n\n\nCopy and paste thoughtfully!\n\n\nNot every piece of code from the early part of the chapter will necessarily apply to the later exercises. And the code that does apply will need to be modified (sometimes quite heavily) to be able to run new analyses. Your job is to understand how the code works so that you can make changes to it without breaking things. If you don’t understand a piece of code, don’t copy and paste it until you’ve read and re-read the earlier exposition that explains how the code works.\n\nOne final note about copying and pasting. Sometimes, people will try to copy and paste code from the HTML output file. This is a bad idea. The HTML document uses special characters to make the output look pretty, but these characters don’t actually work as plain text in a Quarto document. The same applies to things copied and pasted from a Word document or another website. If you need to copy and paste code, be sure to find the plain text Quarto file (the one with the .qmd extension here in RStudio) and copy and paste from that.", "crumbs": [ "2  Using Quarto" ] @@ -314,7 +314,7 @@ "href": "02-using_quarto-web.html#conclusion", "title": "2  Using Quarto", "section": "2.13 Conclusion", - "text": "2.13 Conclusion\nThat’s it! There wasn’t too much you were asked to do for this assignment that will actually show up in the HTML output. (Make sure you did do the three things that were asked of you, however: one was adding your name and the date to the YAML header, one was typing something in the blue answer box, and the last was to make a section header appear properly.) As you gain confidence and as we move into more serious stats material, you will be asked to do a lot more.\n\n2.13.1 Preparing and submitting your assignment\nIf you look in your project folder, you should see three files:\n[a file with a .Rproj extension, either project.Rproj or intro_stats.Rproj]\n02-using_quarto.html\n02-using_quarto.qmd\nThe first file (with extension .Rproj) you were instructed never to touch.\nThe next file has extension .html. That is the pretty output file generated when you hit the “Render” button. This is the “final product” of your work.\nFinally, you have a file with extension .qmd. This is your Quarto file. It’s the file you’re looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run.\n(If you happen to see other files or folders in your project folder, you should ignore those and not mess with them.)\nThere are several steps that you should follow at the end of each of every chapter.\n\nFrom the “Run” menu, select “Restart R and Run All Chunks”.\nDeal with any code errors that crop up. Repeat steps 1–-2 until there are no more code errors.\nSpell check your document by clicking the icon with “ABC” and a check mark.\nHit the “Render” button one last time to generate the final draft of the HTML file. (If there are errors here, you may need to go back and fix broken inline code or other markdown issues.)\nProofread the HTML file carefully. If there are errors, go back and fix them, then repeat steps 1–5 again.\n\nIf you have completed this chapter as part of a statistics course, follow the directions you receive from your professor to submit your assignment.", + "text": "2.13 Conclusion\nThat’s it! There wasn’t too much you were asked to do for this assignment that will actually show up in the HTML output. (Make sure you did do the three things that were asked of you, however: one was adding your name and the date to the YAML header, one was typing something in the blue answer box, and the last was to make a section header appear properly.) As you gain confidence and as we move into more serious stats material, you will be asked to do a lot more.\n\n2.13.1 Preparing and submitting your assignment\nIf you look in your project folder, you should see (at least) three files:\n[a file with a .Rproj extension, either project.Rproj or intro_stats.Rproj]\n02-using_quarto.qmd\n02-using_quarto.html\nThe first file (with extension .Rproj) you were instructed never to touch.\nThe next file has extension .qmd. This is your Quarto file. It’s the file you’re looking at right now. It is really nothing more than a plain text file, although when you open it in RStudio, some magic allows you to see the output from the code chunks you run.\nFinally, you have a file with extension .html. This is the pretty output file generated when you hit the “Render” button. This is the “final product” of your work.\n(If you happen to see other files or folders in your project folder, you should ignore those and not mess with them.)\nThere are several steps that you should follow at the end of each of every chapter.\n\nFrom the “Run” menu, select “Restart R and Run All Chunks”.\nDeal with any code errors that crop up. Repeat steps 1–2 until there are no more code errors.\nSpell check your document by clicking the icon with “ABC” and a check mark.\nHit the “Render” button one last time to generate the final draft of the HTML file. (If there are errors here, you may need to go back and fix broken inline code or other markdown issues.)\nProofread the HTML file carefully. If there are errors, go back and fix them, then repeat steps 1–5 again.\n\nIf you have completed this chapter as part of a statistics course, follow the directions you receive from your professor to submit your assignment.", "crumbs": [ "2  Using Quarto" ]