diff --git a/docs/articles/Starting-a-DRR.html b/docs/articles/Starting-a-DRR.html
index 733b133..a0220b4 100644
--- a/docs/articles/Starting-a-DRR.html
+++ b/docs/articles/Starting-a-DRR.html
@@ -102,8 +102,7 @@ <h2 id="drrs-background">DRRs: Background<a class="anchor" aria-label="anchor" h
 </h2>
 <p><a href="DRR_Purpose_and_Scope.html">Purpose and Scope of Data
 Release Reports</a></p>
-<p>This is a template is for use when drafting Data Release Reports.
-DRRs are created by the National Park Service and provide detailed
+<p>DRRs are created by the National Park Service and provide detailed
 descriptions of valuable research datasets, including the methods used
 to collect the data and technical analyses supporting the quality of the
 measurements. Data Release Reports focus on helping others reuse data
@@ -111,19 +110,23 @@ <h2 id="drrs-background">DRRs: Background<a class="anchor" aria-label="anchor" h
 interpretations and in-depth analyses.</p>
 </div>
 <div class="section level2">
-<h2 id="about-this-template">About this Template<a class="anchor" aria-label="anchor" href="#about-this-template"></a>
+<h2 id="about-the-drr-template">About the DRR Template<a class="anchor" aria-label="anchor" href="#about-the-drr-template"></a>
 </h2>
-<p>This template contains an rmarkdown template file, default folder
-structure for project files, and all the necessary template files to
-generate an unformatted .docx file. Upon submission for publication, the
-.docx file will be ingested by EXstyles, converted to an .xml file and
-fully formatted according to NPS branding upon final publication. The
-goal of this process is to relieve data producers, managers, and
-scientists from the burden of formatting and allow them to focus
-primarily on content. Consequently, the .docx generated for the
-publication process may not be visually appealing. The content, however,
-should focus on the production, quality, and utility of NPS data
-packages.</p>
+<p>Opening a new NPS DRR Template will write a folder to the current
+working directory that contains the an rmarkdown (.rmd) file that is the
+DRR Tempate, a references.bib file for bibtex references, a
+national-park-service-DRR,csl file for formatting references, and a
+sub-folder, BICY_Example with an example data package that can be used
+to knit an example DRR to .docx.</p>
+<p>Upon submission for publication, the .docx file will be ingested by
+EXstyles, converted to an .xml file and fully formatted according to NPS
+branding and in compliance with 508 accessibility requirements upon
+final publication. The goal of this process is to relieve data
+producers, managers, and scientists from the burden of formatting and
+allow them to focus primarily on content. Consequently, the .docx
+generated for the publication process may not be visually appealing. The
+content, however, should focus on the production, quality, and utility
+of NPS data packages.</p>
 </div>
 <div class="section level2">
 <h2 id="how-to-start-a-drr">How to Start a DRR<a class="anchor" aria-label="anchor" href="#how-to-start-a-drr"></a>
@@ -132,11 +135,13 @@ <h2 id="how-to-start-a-drr">How to Start a DRR<a class="anchor" aria-label="anch
 <li><p><strong>To start your DRR you will need all of your data in flat
 .csv files</strong>. All quality assurance, quality control, and quality
 flagging should be completed. Ideally you have already created or are in
-the process of creating a data package. All of the .csv files you want
-to describe in the DRR should be in a single folder with <strong>no
-additional .csv files</strong> (other files such as .txt and .xml will
-be ignored). This folder can be the same folder you used/are using to
-create a data package.</p></li>
+the process of creating a data package (see the <a href="https://nationalparkservice.github.io/EMLeditor/articles/a02_EML_creation_script.html" class="external-link">documentation</a>
+associated with the R package <a href="https://nationalparkservice.github.io/EMLeditor/index.html" class="external-link">EMLeditor</a>
+for data package creation). All of the .csv files you want to describe
+in the DRR should be in a single folder with <strong>no additional .csv
+files</strong> (other files such as .txt and .xml will be ignored). This
+folder can be the same folder you used/are using to create a data
+package.</p></li>
 <li><p><strong>Using Rstudio, open an R project</strong> (Select: File
 &gt; New Project…) in the same folder as your .csv files. If you already
 have an R project (.Rproj) initiated from creating a data package, you
@@ -166,7 +171,7 @@ <h2 id="how-to-start-a-drr">How to Start a DRR<a class="anchor" aria-label="anch
 <ol start="4" style="list-style-type: decimal">
 <li>
 <strong>Open a new DRR Template</strong>. From within Rstudio,
-select the “File” drop down menu. Choose “New File” and then “R
+select the “File” drop down menu. Choose “New File &gt;” and then “R
 markdown…”. This will open up a pop-up dialog box. Select “From
 Template” on in the right-hand list and choose the template labelled
 “NPS_DRR {QCkit}”. You can change the file and folder name to something
@@ -182,8 +187,8 @@ <h2 id="how-to-start-a-drr">How to Start a DRR<a class="anchor" aria-label="anch
 Second, a new folder will be created called “Untitled” (Unless you opted
 to change the default “Name:” in the “New R Markdown” pop up, then these
 will have whatever name you gave them).</p></li>
-<li><p><strong>Edit the DRR Template</strong> according to your
-specifications and the instructions in the <a href="Using-the-DRR-Template.html">“Using the DRR Template”</a>
+<li><p><strong>Edit the DRR Template</strong> to reflect the data you
+would like to descibe and according to the instructions in the <a href="Using-the-DRR-Template.html">“Using the DRR Template”</a>
 guide.</p></li>
 <li><p><strong>“knit” the .rmd file to Word</strong> when you are done
 editing it. Submit the resulting .docx file for publication (via a
@@ -194,10 +199,10 @@ <h2 id="how-to-start-a-drr">How to Start a DRR<a class="anchor" aria-label="anch
 <h2 id="examples">Examples<a class="anchor" aria-label="anchor" href="#examples"></a>
 </h2>
 <p><strong>Knit your own example DRR:</strong> Assuming you left the
-“Name:” as the default “untitled”, you should be able to knit the DRR
+“Name:” as the default “Untitled”, you should be able to knit the DRR
 template in to an example .docx that could be submitted for publication.
 If you opted to change the Name, you will need to update the the file
-paths before kniting.</p>
+paths before knitting.</p>
 </div>
   </div>
 
diff --git a/docs/articles/Using-the-DRR-Template.html b/docs/articles/Using-the-DRR-Template.html
index c605d0f..451e9c7 100644
--- a/docs/articles/Using-the-DRR-Template.html
+++ b/docs/articles/Using-the-DRR-Template.html
@@ -158,24 +158,27 @@ <h3 id="code-chunks">Code Chunks<a class="anchor" aria-label="anchor" href="#cod
 Set to NULL if there is no reportNumber.</li>
 <li>
 <code>DRR_DSRefID</code>. This is the DataStore reference ID for the
-report.</li>
+report. It should be 7 digits long.</li>
 <li>
-<code>authorNames</code>. A list of the author’s names.</li>
+<code>authorNames</code>. A list of the author’s names. If an author
+has multiple institutional affiliations, the author should be listed
+once for each affiliation.</li>
 <li>
 <code>authorAffiliations</code>. A list of the author’s
 affiliations. The order of author affiliations must match the order of
 the authors in the <code>authorNames</code> list. Note that the entirety
-of each affiliation is enclosed in a single set of quotations. Line
-breaks are indicated with the <br> tag. Do not worry about indentation
-or word wrapping. If two authors have the same affiliation, list the
-affiliation twice.</li>
+of each affiliation is enclosed in a single set of quotations. Do not
+worry about indentation or word wrapping. If two authors have the same
+affiliation, list the affiliation twice.</li>
 <li>
 <code>authorORCID</code>. A list of ORCID iDs for each author in the
-format “xxxx-xxxx-xxxx-xxxx”. If an author does not have an ORCID iD,
+format “(xxxx-xxxx-xxxx-xxxx)”. If an author does not have an ORCID iD,
 specify NA (no quotes). The order of ORCID iDs (and NAs) must correspond
-to the order of authors in the <code>authorNames</code> list. Future
-iterations of the DRR Template will pull ORCID iDs from metadata and
-eventually from Active Directory. See <a href="https://www.orcid.org/" class="external-link">ORCID</a> for more information about ORCID
+to the order of authors in the <code>authorNames</code> list. If an
+author was listed more than once in the <code>authorNames</code> list,
+the corresponding ORCID (or NA) should also be listed more than once.
+Future iterations of the DRR Template will pull ORCID iDs from metadata
+and eventually from Active Directory. See <a href="https://www.orcid.org/" class="external-link">ORCID</a> for more information about ORCID
 iDs or to register an ORCID iD.</li>
 <li>
 <code>DRRabstract</code>. The abstract for the DRR (which may be
@@ -209,7 +212,9 @@ <h3 id="code-chunks">Code Chunks<a class="anchor" aria-label="anchor" href="#cod
 <li>
 <code>dataPackage_fileNames</code>. List the file names in your data
 package. Do NOT include metadata files. For example, include
-“my_data.csv” but do NOT include “my_metadata.xml”.</li>
+“my_data.csv” but do NOT include “my_metadata.xml”. Note: Because data
+packages contain only .csv and .xml files, all data files should be
+.csv.</li>
 <li>
 <code>dataPackage_fileSizes</code>. List the approximate size of
 each data file. Make sure the order of the file sizes corresponds to the
@@ -223,8 +228,8 @@ <h3 id="code-chunks">Code Chunks<a class="anchor" aria-label="anchor" href="#cod
 file.</li>
 </ul>
 </li>
-<li><p><code>setup</code>. Most users will not need to edit this code
-chunk. There is one code snippet for loading packages; the
+<li><p><code>setup_do_not_edit</code>. Most users will not need to edit
+this code chunk. There is one code snippet for loading packages; the
 <code>RRpackages</code> section is a suite of packages that are used to
 assist with reproducible reporting. You may not need these for your
 report, but we have included them as part of the base recommended
@@ -240,18 +245,39 @@ <h3 id="code-chunks">Code Chunks<a class="anchor" aria-label="anchor" href="#cod
 chunk. This writes the author names, ORCID iDs, and affiliations to the
 .docx document based on information supplied in
 user-edited-parameters.</p></li>
-<li><p><code>LoadData</code>. Any datasets you need to load can go here.
-For most people these datasets are used to generate summary statistics
-on proportions of data that were flagged as accepted (A) accepted,
-estimated (AE) and rejected (R) during the quality control
-process.</p></li>
-<li><p><code>FileTable</code>. Do not edit. Generates a table of file
+<li><p><code>file_table</code>. Do not edit. Generates a table of file
 names, sizes, and descriptions in the data package being described by
 the DRR.</p></li>
-<li><p><code>dataFlaggingTable</code>. This sample code provides a
-summary table defining the suggested data flagging codes. There is no
-need to edit this table.</p></li>
-<li><p><code>Listing</code>. Appendix A, by default is the code listing.
+<li><p><code>data_acceptance_criteria</code>. If you did not use the
+standard data quality assurance flags (A = accepted, AE = Accepted
+(estimated), R = Rejected, P = Provisional), set this code chunk to
+<code>eval = FALSE</code> and generate your own custom code chunk to
+summarize your custom data flagging procedures. If you did use the
+standard QA flags, indicate which fields in your data files contain
+flagged data. Assuming your column names are unique, you do not need to
+specify which file the columns are in. If your column names are not
+unique, you will need to design your own summary table. Briefly describe
+the acceptance criteria for each data quality flagged column in the same
+order as the you specified the columns.</p></li>
+<li><p><code>data_colunn_flagging</code>. Uses the input from
+<code>data_acceptance_criteria</code> to generate a table summarizing
+the data quality flagging in the data package. If you set
+<code>data_acceptance_criteria</code> parameter
+<code>eval = FALSE</code>, also set <code>data_column_flagging</code>
+parameter to <code>eval = FALSE</code>. Update the first line (which in
+the example points to BICY_Example) to point to the directory where your
+data are.</p></li>
+<li><p><code>data_package_flagging</code>. If you used standard QA flags
+in your data package, leave the parameter <code>eval = TRUE</code>. If
+you did not use standard QA flags, set <code>eval = FALSE</code> and
+design your own custom summary table to handle your custom flagging
+protocols. If you set <code>eval = TRUE</code>, update the file path to
+pointing to your data files (in the example, the path points to the
+directory “BICY_Example”).</p></li>
+<li><p><code>figure1</code>. This is an example code chunk for inserting
+figures. Edit and re-deploy as necessary to include as many or as few
+figures as your require.</p></li>
+<li><p><code>listing</code>. Appendix A, by default is the code listing.
 This will generate all code used in generating the report and data
 packages. In most cases, code listing is not required. If all QA/QC
 processes and data manipulations were performed elsewhere, you should
@@ -259,7 +285,7 @@ <h3 id="code-chunks">Code Chunks<a class="anchor" aria-label="anchor" href="#cod
 code chunk with the default settings of eval=FALSE and echo=FALSE. If
 you have developed custom scripts, you can add those to DataStore with
 the reference”Script” and cite them in the DRR.</p></li>
-<li><p><code>session-info</code> is the information about the versions
+<li><p><code>session_-_info</code> is the information about the versions
 of R and packages used in generating the report. In most cases, you do
 not need to report session info (leave the session-info code chunk
 parameters in their default state: eval=FALSE). Session and version
diff --git a/docs/pkgdown.yml b/docs/pkgdown.yml
index 286504f..ea07434 100644
--- a/docs/pkgdown.yml
+++ b/docs/pkgdown.yml
@@ -5,5 +5,5 @@ articles:
   DRR_Purpose_and_Scope: DRR_Purpose_and_Scope.html
   Starting-a-DRR: Starting-a-DRR.html
   Using-the-DRR-Template: Using-the-DRR-Template.html
-last_built: 2024-02-09T20:53Z
+last_built: 2024-02-12T21:24Z