docs: Fix caching docs to comply with current features.

docs/caching/README.md

@@ -1,33 +1,27 @@
-## Object caching
+## Object Caching
 
-Object caching by turned on by default with following settings
+Object caching is on by default with following settings
 
- - Default cache size 8GB. Cache size also automatically picks
+ - Cache size is 50% of your RAM size. Caching is disabled
-   a lower value if your local memory size is lower than 8GB.
+   if your RAM size is smaller than 8GB.
 
- - Default expiration of entries happensat 72 hours,
+ - Expiration of each entries happen on every 72 hours.
-   this option cannot be changed.
 
- - Default expiry interval is 1/4th of the expiration hours, so
+ - Garbage collection sweep of the expired entries happen every
-   expiration sweep happens across the cache every 1/4th the time
+   1/4th the set expiration hours value (every 18 hours).
-   duration of the set entry expiration duration.
+
+NOTE: None of the settings can be configured manually.
 
 ### Behavior
 
 Caching happens on both GET and PUT operations.
 
 - GET caches new objects for entries not found in cache.
+  Otherwise serves from the cache.
 
-- PUT/POST caches all successfully uploaded objects.
+- PUT/POST caches all successfully uploaded objects. Replaces
-
+  existing cached entry for the same object if needed.
-In all other cases if objects are served from cache.
-
-NOTE:
-
-Cache is always populated upon object is successfully
-read from the disk.
 
-Expiration happens automatically based on the configured
+NOTE: Expiration happens automatically based on the configured
-interval as explained above, frequently accessed objects
+interval as explained above, frequently accessed objects stay
-stay alive for significantly longer time due to the fact
+alive in cache for a significantly longer time on every cache hit.
-that expiration time is reset for every cache hit.