add distinction between guide and tutorial

doc/development/writing_documentation.md

@@ -27,6 +27,14 @@ They live under `doc/topics/topic-name/`, and can be searched per topic, within
 - **Technical Overviews**: technical content describing features, solutions, and third-party integrations
 - **Tutorials**: technical content provided step-by-step on how to do things, or how to reach very specific objectives
 
+#### Understanding Guides and Tutorials
+
+Suppose there's a process to go from point A to point B in 5 steps: (A) 1 > 2 > 3 > 4 > 5 (B).
+
+A **guide** can be understood as a description of certain processes to achieve a particular objective. A guide brings you from A to B describing the characteristics of that process, but not necessarily going over each step. It can mention, for example, the step 3, but, assumes that that step is known by the reader, or out of the scope of that article.
+
+A **tutorial** requires a clear **step-by-step** guidance to achieve a singular objective. It brings you from A to B, describing precisely all the necessary steps involved in that process, showing each of the 5 steps to go from A to B. It does not assume that you step 3: it shows you each of them.
+
 #### Special Format
 
 Every **Technical Article** contains, in the very beginning, a blockquote with the following information: