Fixes #5 . A note on flaky annotation usage.

docs/2.0/features.adoc

@@ -3,4 +3,6 @@ This section describes the main features of Allure.
 For example, you can group your tests by stories or features, attach files, and distribute assertions over a
 set of custom steps, among other features. All features are supported by Java test frameworks, so we only provide
 Java examples here. For details on how a particular adapter works with the test framework of your choice,
-refer to the adapter guide.
+refer to the adapter guide.
+
+include::features/flaky.adoc[leveloffset=+1]

docs/2.0/features/flaky.adoc

@@ -0,0 +1,20 @@
+= Flaky tests
+
+In a real life not all of your tests are stable and always green or always red.  A test might start to "blink" i.e. it fails from time-to-time without any obvious reason.
+You could disable such a test, that is a trivial solution. However what if you do not want to do that?
+Say you would like to get more details on possible reasons or the test is so critical that even being flaky it provides helpful information?
+You have an option now to mark such tests in a special way, so resulting report will clearly show them as unstable:
+
+[source, java]
+----
+@Flaky
+public void aTestWhichFailsFromTimeToTime {
+     ...
+}
+----
+
+Here is what you get in the report in case if such test failed:
++
+image::flaky_failed.png[A failed test marked as flaky]
+
+Additional note - you could mark a whole test class as flaky as well.