Updated readme

Author: rennokki

README.md

@@ -135,24 +135,9 @@ class Kid extends Model
 Kid::flushQueryCache();
 ```
 
-## Relationship Caching
-
-Relationships are just another queries. They can be intercepted and modified before the database is hit with the query. The following example needs the `Order` model (or the model associated with the `orders` relationship) to include the `QueryCacheable` trait.
-
-```php
-$user = User::with(['orders' => function ($query) {
-    return $query
-        ->cacheFor(60 * 60)
-        ->cacheTags(['my:orders']);
-}])->get();
-
-// This comes from the cache if existed.
-$orders = $user->orders;
-```
-
 ## Full Automatic Invalidation
 
-To speed up the scaffolding of invalidation within your app, you can specify the model to auto-flush the cache upon any model gets created, updated or deleted.
+To speed up the scaffolding of invalidation within your app, you can specify the model to auto-flush the cache upon any time records gets created, updated or deleted.
 
 ```php
 class Page extends Model
@@ -224,6 +209,21 @@ $page->update([
 
 **Not specifying a tag to invalidate fallbacks to the set of base tags, thus leading to Full Automatic Invalidation.**
 
+## Relationship Caching
+
+Relationships are just another queries. They can be intercepted and modified before the database is hit with the query. The following example needs the `Order` model (or the model associated with the `orders` relationship) to include the `QueryCacheable` trait.
+
+```php
+$user = User::with(['orders' => function ($query) {
+    return $query
+        ->cacheFor(60 * 60)
+        ->cacheTags(['my:orders']);
+}])->get();
+
+// This comes from the cache if existed.
+$orders = $user->orders;
+```
+
 ## Cache Keys
 
 The package automatically generate the keys needed to store the data in the cache store. However, prefixing them might be useful if the cache store is used by other applications and/or models and you want to manage the keys better to avoid collisions.