rails · nisusam · Feb 27, 2026 · Feb 27, 2026
diff --git a/_companies/clio.md b/_companies/clio.md
@@ -22,7 +22,7 @@ member_status: "In 2025, Company became a **contributing member** of the Rails F
 github_contributions:
   - name: "jit_preloader"
     url: "https://github.com/clio/jit_preloader"
-  - name: "polymoprhic_integer_type"
+  - name: "polymorphic_integer_type"
     url: "https://github.com/clio/polymorphic_integer_type"
   - name: "dead_code_detector"
     url: "https://github.com/clio/dead_code_detector"

diff --git a/_companies/template.md b/_companies/template.md
@@ -23,7 +23,7 @@ member_status: "In 2022, Company became a **founding Core member** of the Rails
 github_contributions:
   - name: "rails"
     url: "https://github.com/rails/rails"
-contribution_string: "detail abotu contributions if don't want to link to repositories"
+contribution_string: "detail about contributions if don't want to link to repositories"
 community: |
   [Item to link](https://www.com) - Description of contribution
 case_study_blurb: "Check out the case study of how company delivers incredible value to its customers with Rails"

diff --git a/...4-lots-of-active-storage-goodies-and-many-quality-of-life-improvements.markdown b/...4-lots-of-active-storage-goodies-and-many-quality-of-life-improvements.markdown
@@ -57,7 +57,7 @@ You should be calling these methods directly on the attachment and not on the as
 
 You may be familiar with the instance method Model#update!, but now you can do that on the class!
 
-### [Performance regression in CollectionAssocation#build](https://github.com/rails/rails/pull/42524)
+### [Performance regression in CollectionAssociation#build](https://github.com/rails/rails/pull/42524)
 
 This fixes a huge performance bug for inversing associations with a lot of records.
 

diff --git a/...s-week-in-rails-perform-destroy_all-in-batches-and-a-lot-more-features.markdown b/...s-week-in-rails-perform-destroy_all-in-batches-and-a-lot-more-features.markdown
@@ -18,7 +18,7 @@ By default it will load records in batches of 100 and allow to specify the custo
 A valid ordinal value will be converted to an instance of _TimeWithZone._  
 In example "21087" value will be parsed to 28-03-2021 date.
 
-### [Add existence check to foregin key migrations](https://github.com/rails/rails/pull/42616)
+### [Add existence check to foreign key migrations](https://github.com/rails/rails/pull/42616)
 
 It is now possible to use _if\_exists / if\_not\_exist_ on _remove\_foreign\_key / add\_foreign\_key_ in database migrations.
 

diff --git a/...2024-12-10-Rails-Versions-8-0-0-1-7-2-2-1-7-1-5-1-7-0-8-7-have-been-released.md b/...2024-12-10-Rails-Versions-8-0-0-1-7-2-2-1-7-1-5-1-7-0-8-7-have-been-released.md
@@ -19,7 +19,7 @@ We think this usage will be rare, and the default configuration is not
 vulnerable, but advise upgrading.
 
 Older versions of Rails are unsupported, and users are recommended to upgrade
-to at least the 7.0 series, which will be receiveing security updates until
+to at least the 7.0 series, which will be receiving security updates until
 April. See our [maintenance policy](https://rubyonrails.org/maintenance) for details.
 
 Here is a list of security issues that these releases address:

diff --git a/_posts/2025-01-10-this-week-in-rails.markdown b/_posts/2025-01-10-this-week-in-rails.markdown
@@ -36,7 +36,7 @@ This fixes a very old regression introduced in Rails 5.1!
 The table columns inside `schema.rb` are now sorted alphabetically.
 Previously they'd be sorted by creation order, which can cause merge conflicts when two branches modify the same table concurrently.
 
-[Update NotificationAssertions's assert_notifcation to match against payload subsets and return matched notification](https://github.com/rails/rails/pull/54126)  
+[Update NotificationAssertions's assert_notification to match against payload subsets and return matched notification](https://github.com/rails/rails/pull/54126)
 `ActiveSupport::Testing::NotificationAssertions`'s `assert_notification` now matches against payload subsets by default.
 
 Previously the following assertion would fail due to excess key values in the notification payload. Now with payload subset matching, it will pass.

diff --git a/_posts/2025-05-09-this-week-in-rails.markdown b/_posts/2025-05-09-this-week-in-rails.markdown
@@ -28,7 +28,7 @@ This update ensures that when a retryable `SqlLiteral` is provided to `#where`,
 This change updates Active Record's SQLite adapter to represent boolean values as `TRUE` and `FALSE` instead of 1 and 0. This enhances SQL readability and aligns with standard SQL boolean literals.
 
 [Make the executor hooks in AR::QueryCache private](https://github.com/rails/rails/pull/55007)  
-`ActiveRecord::QueryCache` has been refactored to make its executor hooks private, ensuring they're not accessible or overrideable externally. Additionally, it reorganizes these hooks for improved clarity, aligning with the structure used in the connection pool.
+`ActiveRecord::QueryCache` has been refactored to make its executor hooks private, ensuring they're not accessible or overridable externally. Additionally, it reorganizes these hooks for improved clarity, aligning with the structure used in the connection pool.
 
 [Rescue connection related errors in MemCacheStore#read_multi_entries](https://github.com/rails/rails/pull/55000)  
 This change enhances the `MemCacheStore#read_multi_entries` method by adding error handling for connection-related issues. Previously, network interruptions during bulk reads from Memcached could cause failures; such errors are now properly rescued, improving resilience in distributed caching scenarios.

diff --git a/_posts/2025-08-23-this-week-in-rails.markdown b/_posts/2025-08-23-this-week-in-rails.markdown
@@ -19,7 +19,7 @@ has been updated.
 This pull request fixes the removal of _pg_dump_'s versioning comments by also removing the new `\restrict` lines. By removing all these lines, the generated _structure.sql_ can again be consistent between runs of `rails db:schema:dump` on the latest versions of PostgreSQL.
 
 [Allow _current_page?_ to match against specific HTTP method(s) with a _method:_ option](https://github.com/rails/rails/pull/55286)  
-Before this chage, the `current_page?` helper only matched on GET and HEAD
+Before this change, the `current_page?` helper only matched on GET and HEAD
 requests, but with the new optional `method` option, it will match against
 explicit HTTP methods.
 

diff --git a/_posts/2025-09-04-rails-8-1-beta-1.markdown b/_posts/2025-09-04-rails-8-1-beta-1.markdown
@@ -92,7 +92,7 @@ Structured Event Reporting was lead by Adrianna Chang from [Shopify](https://sho
 
 Developer machines have gotten incredibly quick with loads of cores, which make them great local runners of even relatively large test suites. The [HEY](https://hey.com/) test suite of over 30,000 assertions used to take over 10 minutes to run in the cloud when counting coordination, image building, and parallelized running. Now it runs locally on a Framework Desktop AMD Linux machine in just 1m 23s and an M4 Max in 2m 22s.
 
-This makes getting rid of a cloud-setup for all of CI not just feasible but desireable for many small-to-mid-sized applications, and Rails has therefore added a default CI declaration DSL, which is defined in `config/ci.rb` and run by `bin/ci`. It looks like this:
+This makes getting rid of a cloud-setup for all of CI not just feasible but desirable for many small-to-mid-sized applications, and Rails has therefore added a default CI declaration DSL, which is defined in `config/ci.rb` and run by `bin/ci`. It looks like this:
 
 ```ruby
 CI.run do

diff --git a/_posts/2025-10-31-this-week-in-rails.markdown b/_posts/2025-10-31-this-week-in-rails.markdown
@@ -15,7 +15,7 @@ Hi, [Wojtek](https://x.com/morgoth85) here. 🎃 Let's see if there are any spoo
 Versions 7.0.10, 7.1.6, 7.2.3, 8.0.4, and 8.1.1 have been released.
 Rails 8.0 has received extended support.
 
-[Add a summary report at the end of Continous Integration run](https://github.com/rails/rails/pull/56049)  
+[Add a summary report at the end of Continuous Integration run](https://github.com/rails/rails/pull/56049)
 The *@results* ivar is changed to hold the step title in addition to the success boolean, and any multi-step *run* or *step* block will print the failed steps.
 The output looks like:
 ```

diff --git a/_posts/2025-12-26-this-week-in-rails.markdown b/_posts/2025-12-26-this-week-in-rails.markdown
@@ -131,7 +131,7 @@ ActionMailer.deliver_all_later(user_emails)
 ```
 
 [Allow current_page? to match against specific HTTP method(s) with a method: option](https://github.com/rails/rails/pull/55286)  
-Before this chage, the `current_page?` helper only matched on GET and HEAD requests, but with the new optional method option, it will match against explicit HTTP methods.
+Before this change, the `current_page?` helper only matched on GET and HEAD requests, but with the new optional method option, it will match against explicit HTTP methods.
 
 [Add markdown mime type and renderer](https://github.com/rails/rails/pull/55511)  
 Add .md/.markdown as Markdown extensions and add a default `markdown:` renderer: