Merge branch 'contrib/17809-etcher-responsibility'

wiki/src/contribute/working_together/roles/technical_writer.mdwn

@@ -13,11 +13,11 @@ as a fallback if no other contributor volunteers to do it.
     Changelog excerpts provided by RM.
   - Redacting exceptional publications on our
     blog (security advisory, etc.) or reviewing
-    them against GDSG and the rest of our documentation.
-  - Reviewing contributions of paid workers to our end-user
-    documentation (/doc and /support) against GDSG and consistency
-    with the rest of our documentation. For example, the [[Foundations Team]]
-    sometimes write known issues.
+    them against our style guide.
+  - Reviewing contributions by paid workers to our end-user
+    documentation (/doc and /support) against our style guide.
+    For example, the [[Foundations Team]]
+    sometimes writes known issues.
   - Maintaining a style guide of Tails-related terms and usage to
     summarizes the terminology decision taken elsewhere.
   - Documenting new features, including [[doc/about/features]].
@@ -29,6 +29,10 @@ as a fallback if no other contributor volunteers to do it.
     provided by our Help Desk and triaged by the Foundations Team.
   - Keeping our documentation and support pages efficient for the people
     reading them (relevant and easy to navigate).
+  - Maintain our documentation on tools that are not part of Tails but
+    that we instruct people to use. For example,
+    testing, updating, and debugging *Etcher* or the Secure Boot utilities
+    of macOS.
 
 As technical writers have a limited amount of time to dedicate to these
 tasks, Tails as a project should redefine priorities on a regular basis.