large progress on guide

Don't have enough time to complete and copy-edit this now though.

1 files changed, 7 insertions, 6 deletions

diff --git a/guide/src/workflow.md b/guide/src/workflow.md
index 13370a13..fd53f6a9 100644
--- a/guide/src/workflow.md
+++ b/guide/src/workflow.md
@@ -9,7 +9,7 @@ software.
 The normal workflow is to create edits (or updates, merges, deletions) on
 individual entities. Individual changes are bundled into an "edit group" of
 related edits (eg, correcting authorship info for multiple works related to a
-single author). When ready, the editor would "submit" the edit group for
+single author). When ready, the editor "submits" the edit group for
 review. During the review period, human editors vote and bots can perform
 automated checks. During this period the editor can make tweaks if necessary.
 After some fixed time period (72 hours?) with no changes and no blocking
@@ -28,9 +28,10 @@ Data progeny and source references are captured in the edit metadata, instead
 of being encoded in the entity data model itself. In the case of importing
 external databases, the expectation is that special-purpose bot accounts
 are be used, and tag timestamps and external identifiers in the edit metadata.
-Human editors would leave edit messages to clarify their sources.
+Human editors can leave edit messages to clarify their sources.
+
+A [style guide](./style_guide.md) and discussion forum are intended to be be
+hosted as separate stand-alone services for editors to propose projects and
+debate process or scope changes. These services should have unified accounts
+and logins (oauth?) for consistent account IDs across all services.
 
-A style guide (wiki) and discussion forum would be hosted as separate
-stand-alone services for editors to propose projects and debate process or
-scope changes. These services should have unified accounts and logins (oauth?)
-to have consistent account IDs across all mediums.