Follow up tweaks b89a3e7e63 [ci skip]

* use backticks instead of `+`
* and more (e.g. missed replacing `Array#excluding` and
`Enumerable#excluding` in b89a3e7e63)

actionpack/CHANGELOG.md

@@ -43,7 +43,7 @@
 
     *Rafael Mendonça França*
 
-*   Introduce ActionDispatch::HostAuthorization
+*   Introduce `ActionDispatch::HostAuthorization`.
 
     This is a new middleware that guards against DNS rebinding attacks by
     explicitly permitting the hosts a request can be made to.
@@ -73,7 +73,7 @@
 
 *   Raise an error on root route naming conflicts.
 
-    Raises an ArgumentError when multiple root routes are defined in the
+    Raises an `ArgumentError` when multiple root routes are defined in the
     same context instead of assigning nil names to subsequent roots.
 
     *Gannon McGibbon*

activejob/CHANGELOG.md

@@ -34,7 +34,7 @@
 
     *Edouard Chin*
 
-*   Restore HashWithIndifferentAccess support to ActiveJob::Arguments.deserialize.
+*   Restore `HashWithIndifferentAccess` support to `ActiveJob::Arguments.deserialize`.
 
     *Gannon McGibbon*
 

activerecord/CHANGELOG.md

@@ -348,7 +348,7 @@
 
     *Gannon McGibbon*
 
-*   Cached columns_hash fields should be excluded from ResultSet#column_types
+*   Cached `columns_hash` fields should be excluded from `ResultSet#column_types`.
 
     PR #34528 addresses the inconsistent behaviour when attribute is defined for an ignored column. The following test
     was passing for SQLite and MySQL, but failed for PostgreSQL:
@@ -379,12 +379,12 @@
 
 *   Make the implicit order column configurable.
 
-    When calling ordered finder methods such as +first+ or +last+ without an
+    When calling ordered finder methods such as `first` or `last` without an
     explicit order clause, ActiveRecord sorts records by primary key. This can
     result in unpredictable and surprising behaviour when the primary key is
     not an auto-incrementing integer, for example when it's a UUID. This change
     makes it possible to override the column used for implicit ordering such
-    that +first+ and +last+ will return more predictable results.
+    that `first` and `last` will return more predictable results.
 
     Example:
 
@@ -530,10 +530,10 @@
 
 *   Enum raises on invalid definition values
 
-    When defining a Hash enum it can be easy to use [] instead of {}. This
+    When defining a Hash enum it can be easy to use `[]` instead of `{}`. This
     commit checks that only valid definition values are provided, those can
     be a Hash, an array of Symbols or an array of Strings. Otherwise it
-    raises an ArgumentError.
+    raises an `ArgumentError`.
 
     Fixes #33961
 

activesupport/CHANGELOG.md

@@ -61,7 +61,7 @@
 
     *Kaan Ozkan*, *Sharang Dashputre*
 
-*   Allow Array#excluding and Enumerable#excluding to deal with a passed array gracefully.
+*   Allow `Array#excluding` and `Enumerable#excluding` to deal with a passed array gracefully.
 
         [ 1, 2, 3, 4, 5 ].excluding([4, 5]) # => [ 1, 2, 3 ]