Add latest changes from gitlab-org/gitlab@master

1 files changed, 14 insertions, 8 deletions

diff --git a/doc/development/documentation/topic_types/tutorial.md b/doc/development/documentation/topic_types/tutorial.md
index c8e45b7069f..b75b1e6b629 100644
--- a/doc/development/documentation/topic_types/tutorial.md
+++ b/doc/development/documentation/topic_types/tutorial.md
@@ -13,13 +13,17 @@ In general, you might consider using a tutorial when:
   of sub-steps.
 - The steps cover a variety of GitLab features or third-party tools.
 
-Tutorials are not [tasks](task.md). A task gives instructions for how to complete
-a procedure. A tutorial combines different tasks to achieve a specific goal. At
-the end of a tutorial, you have a working example of something.
-
-Tutorials are learning aids that complement our core documentation.
-They do not introduce new features.
-Always use the primary [topic types](index.md) to document new features.
+## Tutorial guidance
+
+- Tutorials are not [tasks](task.md). A task gives instructions for one procedure.
+  A tutorial combines multiple tasks to achieve a specific goal.
+- Tutorials provide a working example. Ideally the reader can create the example the
+  tutorial describes. If they can't replicate it exactly, they should be able
+  to replicate something similar.
+- Tutorials do not introduce new features.
+- Tutorials do not need to adhere to the Single Source of Truth tenet. While it's not
+  ideal to duplicate content that is available elsewhere, it's worse to force the reader to
+  leave the page to find what they need.
 
 ## Tutorial format
 
@@ -35,7 +39,9 @@ To create a website:
 1. [Do the first task](#do-the-first-task)
 1. [Do the second task](#do-the-second-task)
 
-Prerequisites (optional):
+## Prerequisites
+
+This topic is optional.
 
 - Thing 1
 - Thing 2