Typo fix

README.md

@@ -133,7 +133,7 @@ Besides the classic pagination `nav`, Pagy offers a few ready to use alternative
 - [Stateful Tabs with Pagy](https://www.imaginarycloud.com/blog/how-to-paginate-ruby-on-rails-apps-with-pagy) by Chris Seelus
 - [Quick guide for Pagy with Sinatra and Sequel](https://medium.com/@vfreefly/how-to-use-pagy-with-sequel-and-sinatra-157dfec1c417) by Victor Afanasev
 - [Integrating Pagy with Hanami](http://katafrakt.me/2018/06/01/integrating-pagy-with-hanami/) by Paweł Świątkowski
-- [Detailed Gems Comparison](https://ddnexus.github.io/pagination-comparison/gems.html) (charts and analisys)
+- [Detailed Gems Comparison](https://ddnexus.github.io/pagination-comparison/gems.html) (charts and analysis)
 - [Benchmarks and Memory Profiles Source](http://github.com/ddnexus/pagination-comparison) (Rails app repository)
 
 ### Docs
@@ -149,7 +149,7 @@ Besides the classic pagination `nav`, Pagy offers a few ready to use alternative
 
 ## Please Star and Share!
 
-Pagy is young and needs to be known, and **you** can really help, even with just a click on the star, or sharing a tweet with friends and collegues. A big thank you for your support!
+Pagy is young and needs to be known, and **you** can really help, even with just a click on the star, or sharing a tweet with friends and colleagues. A big thank you for your support!
 
 ## Help Wanted
 
@@ -171,7 +171,7 @@ The `dev` branch is kept rebased on top of `master`, so expect it to be force-re
 
 ## Credits
 
-Many thansk to:
+Many thanks to:
 
 - [Imaginary Cloud](https://www.imaginarycloud.com), for continually publishing high-interest articles and helping share Pagy through their fantastic blog
 - [JetBrains](http://www.jetbrains.com) for their free OpenSource license

docs/extras/countless.md

@@ -25,7 +25,7 @@ In a controller:
 @pagy, @records  = pagy_countless(some_scope, ...)
 ```
 
-**Notice**: When using `ActiveRecord`, the `@records` is an `Array`. Onthe other side, the normal `Pagy` returns an `ActiveRelation`.
+**Notice**: When using `ActiveRecord`, the `@records` is an `Array`. On the other side, the normal `Pagy` returns an `ActiveRelation`.
 
 ## Files
 

docs/how-to.md

@@ -101,7 +101,7 @@ You can also pass it as an instance variable to the `Pagy.new` method or to the
 @pagy, @records = pagy(Product.some_scope, items: 30)
 ```
 
-If you want to allow the client to request a custom number of items per page - useful with APIs or higly user-customizable apps - take a look at the [items extra](extras/items.md). It manages the number of items per page requested with the params, and offers a ready to use selector UI.
+If you want to allow the client to request a custom number of items per page - useful with APIs or highly user-customizable apps - take a look at the [items extra](extras/items.md). It manages the number of items per page requested with the params, and offers a ready to use selector UI.
 
 ## Controlling the page links
 
@@ -123,7 +123,7 @@ pagy.series
 #=> [1, 2, 3, :gap, 6, 7, 8, 9, "10", 11, 12, 13, 14, :gap, 48, 49, 50]
 ```
 
-As you can see by the result of the `series` method, you get 3 initial pages, 1 `:gap` (series interupted), 4 pages before the current page, the current `:page` (which is a string), 4 pages after the current page, another `:gap` and 3 final pages.
+As you can see by the result of the `series` method, you get 3 initial pages, 1 `:gap` (series interrupted), 4 pages before the current page, the current `:page` (which is a string), 4 pages after the current page, another `:gap` and 3 final pages.
 
 You can easily try different options (also asymmetrical) in a console by changing the `:size`. Just check the `series` array to see what it contains when used in combination with different core variables.