Move the assertions tricky feature to the end of the list (AdevintaSp…

…ain#348)

Just to keep it coherent

README.md

@@ -325,10 +325,6 @@ assertTextColorIsNot(R.id.customTextView, R.styleable.SampleCustomView, R.style.
 assertRecyclerViewItemCount(R.id.recycler, 10);
 ```
 
-#### And another tricky feature
-```java
-assertThatBackButtonClosesTheApp();
-```
 #### Is this ImageView showing a drawable?
 ```java
 assertHasAnyDrawable(R.id.image_view);
@@ -345,6 +341,11 @@ assertProgressIsMin(R.id.seek_bar)
 assertProgressIsMax(R.id.seek_bar)
 ```
 
+#### And another tricky feature
+```java
+assertThatBackButtonClosesTheApp();
+```
+
 ### Custom assertions
 
 If you have a special case not covered by the given assertions API, we encourage you to assert these special cases with our custom assertions API. It's a convenient way to replace plain `Matcher`s with complex assertions. With Barista, you can match any kind of view by knowing its type and passing its `viewId`, `text`, or a `Matcher<View>`. Once you matched it, you will be able to assert all its properties without adding any complex `Matcher` to your project.