Merge branch 'release/0.1.3'

Author: pbchase

CITATION.cff

@@ -60,5 +60,5 @@ identifiers:
 - type: doi
   value: 10.5281/zenodo.15837864
 license: Apache-2.0
-version: 0.1.2
-date-released: '2025-07-09'
+version: 0.1.3
+date-released: '2025-11-03'

DESCRIPTION

@@ -1,7 +1,7 @@
 Package: participantFlowDiagram
 Type: Package
 Title: Graphically shows the progress of research participants through a study protocol
-Version: 0.1.2
+Version: 0.1.3
 Authors@R: c(
   person("Philip", "Chase",
         email = "pbc@ufl.edu",

NEWS.md

@@ -1,3 +1,6 @@
+# participantFlowDiagram 0.1.3 (released 2025-11-03)
+- Fix grammar and update wording in Getting-Started.Rmd (@pbchase)
+
 # participantFlowDiagram 0.1.2 (released 2025-07-09)
 - Fix label in example diagram and table (@pbchase)
 - Fix reference to gtsummary::tbl_summary() (@pbchase)

vignettes/articles/Getting-Started.Rmd

@@ -98,8 +98,8 @@ create_table(
 
 Using `participantFlowDiagram` requires a detailed dataset, `participant_level_progress`, that documents each step in the workflow. The dataset has multiple constraints:
 
-- Each column must be as a factor. Each level in the factor is a possible state at that step.
-- Each factor should define all possible levels at that step. This in includes an unknown level to be set when no other logic at that level is true.
+- Each column must be a factor. Each level in the factor is a possible state at that step.
+- Each factor should define all possible levels at that step. This should include an "unknown" level to be set when no other logic at that level is true.
 - Each factor value needs to be unique across all the factors because the factor values will be nodes names in a diagram. It is easy to manage this by prefixing each factor level with the column name.
 - The steps should appear in the order of the workflow as this order governs the order in the table. While not required, this will improve the readability of the summary table.
 - At each step, the count of non-null values should equal the count for the parent node. 
@@ -119,7 +119,7 @@ The second required dataset is a small, two-column dataset that names the parent
 steps
 ```
 
-A third dataset, `pretty_labels`, can be generated with the package function `get_pretty_labels_template()` 
+A third dataset, `pretty_labels`, should be generated with the package function `get_pretty_labels_template()`
 
 ```{r describe-pretty-labels}
 pretty_labels_template <- get_pretty_labels_template(
@@ -170,7 +170,7 @@ diagram
 ```
 
 
-To get control of the labels, save the output of `get_pretty_labels_template()` and edit the `pretty_label` column. You can write tribble code using `timesaveR::to_tribble()` to write tribble code and paste that inline in your code. `get_pretty_labels_template()` uses the same value as `plain_label` in  `pretty_label`. Edit the `pretty_label` column as needed. 
+To get control of the labels, save the output of `get_pretty_labels_template()` and edit the `pretty_label` column. The easiest path is to use `timesaveR::to_tribble()` to write tribble code and paste that inline in your code. `get_pretty_labels_template()` uses the same value as `plain_label` in  `pretty_label`. Edit the `pretty_label` column as needed get the labels you'd like to see on the nodes.
 
 Use `\n` to get new line characters to wrap the text of the pretty labels in the diagram. These newline codes will be ignored in the table.