replaced efficiency table with resource-consumption chart; other mino…

…r fixes

.rubocop.yml

@@ -1,5 +1,5 @@
 AllCops:
-  TargetRubyVersion: 2.3
+  TargetRubyVersion: 2.5
 
 Layout:
   Enabled: false

README.md

@@ -38,9 +38,11 @@ The values shown in the charts below have been recorded while each gem was produ
 
 ### ~ 850x More Efficient!
 
-[![Efficiency Table](docs/assets/images/efficiency-table.png)](https://ddnexus.github.io/pagination-comparison/gems.html#efficiency-ratio)
+[![Resource Consumption Chart](docs/assets/images/resource-consumption-chart.png)](https://ddnexus.github.io/pagination-comparison/gems.html#efficiency-ratio)
 
-_The [IPS/Kb ratio](http://ddnexus.github.io/pagination-comparison/gems.html#efficiency-ratio) is calculated out of speed (IPS) and Memory (Kb): it shows how well each gem uses any Kb of memory it allocates/consumes._
+_Each dot in the chart represents the resources that Pagy consumes for one full rendering. The other gems consume hundreds of times as much for the same rendering._
+
+_The [IPS/Kb ratio](http://ddnexus.github.io/pagination-comparison/gems.html#efficiency-ratio) is calculated out of speed (IPS) and Memory (Kb): it shows how well each gem uses each Kb of memory it allocates/consumes._
 
 #### Disclaimer
 
@@ -57,7 +59,7 @@ Please check the [Benchmarks and Memory Profiles Source](http://github.com/ddnex
 - Pagy has a very slim core code of just ~100 lines of simple ruby, organized in 3 flat modules, very easy to understand and use _(see [more...](https://ddnexus.github.io/pagy/api))_
 - It has a quite fat set of optional extras that you can explicitly require for very efficient and modular customization _(see [extras](https://ddnexus.github.io/pagy/extras))_
 - It has no dependencies: it produces its own HTML, URLs, i18n with its own specialized and fast code _(see [why...](https://ddnexus.github.io/pagy/index#specialized-code-instead-of-generic-helpers))_
-- 100% of its methods are public API, accessible and overridable **right where you use them** (no pesky monkey-patching neededneed for )
+- 100% of its methods are public API, accessible and overridable **right where you use them** (no pesky monkey-patching needed)
 - 100% test coverage for core code and extras
 
 ### Totally Agnostic
@@ -128,7 +130,7 @@ Use the official extras, or write your own in just a few lines. Extras add speci
 - [support](http://ddnexus.github.io/pagy/extras/support): Extra support for features like: incremental, infinite, auto-scroll pagination
 - [trim](http://ddnexus.github.io/pagy/extras/trim): Remove the `page=1` param from the first page link
 
-### Alternative components
+### Alternative Components
 
 Besides the classic pagination `nav`, Pagy offers a few ready to use alternatives like:
 

docs/extras/searchkick.md

@@ -74,7 +74,7 @@ This method accepts the same arguments of the `search` method and you must use i
 
 ## Methods
 
-This extra adds the `pagy_searchkick` method to the `Pagy::Backend` to be used when you have to paginate a `Searchkick::Results` object. It also adds a `pagy_searchkick_get_variables` sub-method, used for easy customization of variables by overriding.
+This extra adds the `pagy_searchkick` method to the `Pagy::Backend` to be used when you have to paginate a `Searchkick::Results` object. It also adds a `pagy_searchkick_get_vars` sub-method, used for easy customization of variables by overriding.
 
 ### pagy_searchkick(Model.pagy_search(...), vars={}})