tabs primary use case clarification
-# Fenced Block
+# Primary Use Case
+
+Imagine your product supports multiple ways of achieving a final result:
+* REST
+* Web
+* CLI
+* Java
+* Python
+* etc
+
+Provide a selection inside your documentation if your user needs only one to accomplish her goals.
+Her selection will be remembered and will provide streamlined experience.
+
+Do not: use tabs as navigation experience.
+If your user needs both `Java` and `Python` executed one by one you need to show steps one after another in proper order.
+
+# Definition
To define multiple tabs we use fenced code block
