From c78ed7666478d18065bb2d82d8a97d3d4b00ba5c Mon Sep 17 00:00:00 2001
From: Hadley Wickham <h.wickham@gmail.com>
Date: Mon, 21 Feb 2022 15:54:38 -0600
Subject: [PATCH] Update chapter status

---
 workflow-scripts.Rmd | 4 ++++
 workflow-style.Rmd   | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/workflow-scripts.Rmd b/workflow-scripts.Rmd
index f172cef..2b18b6e 100644
--- a/workflow-scripts.Rmd
+++ b/workflow-scripts.Rmd
@@ -1,5 +1,9 @@
 # Workflow: scripts and projects
 
+```{r, results = "asis", echo = FALSE}
+status("restructuring")
+```
+
 So far you've been using the console to run code.
 That's a great place to start, but you'll find it gets cramped pretty quickly as you create more complex ggplot2 graphics and dplyr pipes.
 To give yourself more room to work, it's a great idea to use the script editor.
diff --git a/workflow-style.Rmd b/workflow-style.Rmd
index 552e6af..026557a 100644
--- a/workflow-style.Rmd
+++ b/workflow-style.Rmd
@@ -1,7 +1,7 @@
 # Workflow: code style {#workflow-style}
 
 ```{r, results = "asis", echo = FALSE}
-status("drafting")
+status("polishing")
 ```
 
 Good coding style is like correct punctuation: you can manage without it, butitsuremakesthingseasiertoread.