Development/Dataworker-Development-Workflow.md

@@ -18,18 +18,18 @@ development pipeline, from first discussion to validation.
 > We no longer use the `proposal` status. We use instead new tickets without
 > status.
 
-> We no longer use the `done` column. We now `close` all tickets and assign these a `done` or `canceled` status as needed.
+> We no longer use the `done` column. We now **close** all tickets and assign these a `done` or `canceled` status as needed.
 
 ## Discussion
 
-If the subject is complex, we start with a discussion page that describe the
+If the subject is complex, we start with a discussion page that describes the
 context of the issue, the issue, and direction for a solution. We link the
 discussion in the [Dataworker Home Page](Development/DataWorker-Home).
 
 ## Open issue ticket
 
 Once the discussion leads to a design decision, we can start creating issues in
-the issue tracker using the `dataworker` tag. New dataworker issues are visible
+the issue tracker, labeling them with the `dataworker` tag. New dataworker issues are visible
 in the [Dataworker Issue
 Tracker](https://gitlab.com/prospect-energy/prospect-server/-/boards/5718325?label_name[]=dataworker)
 in the `Open` column.
@@ -42,8 +42,7 @@ effect.
 
 ## Current sprint
 
-An extra step for ready tickets, that should be picked up in priority.
-
+An extra step for ready tickets that should be picked up in priority.
 
 ## In progress
 
@@ -58,5 +57,5 @@ actively monitored.
 
 Once an issue fix is validated, we can close it, and it will no longer be
 visible in the issue dashboard. Before closing we change manually the status
-from `validation` to either `done` or `canceled`, to avoid the unclarity of a
-ticket both closed and with a `validation` label.
+from `validation` to either `done` or `canceled`, to avoid the confusion of a
+ticket both being closed and with a `validation` label.
\ No newline at end of file