diff --git a/Changes b/Changes
index 7f75973bb..40e3cb6a1 100644
--- a/Changes
+++ b/Changes
@@ -1827,26 +1827,26 @@
 - set::level-on-join now also supports voice, halfop, protect and owner.
   Requested by katsklaw (#0003852). Partial patch provided by katsklaw and
   morpheus_pl.
-- Added support for "chained" extbans. Put simply this allows extban combinations
+- Added support for "stacked" extbans. Put simply this allows extban combinations
   such as ~q:~c:#test to only silence users on #test, for example. This feature
   is enabled by default, but can be disabled during ./Config -advanced. Module
   support for this feature must note the following:
   - For is_ok function, the extban can either assign extban_is_ok_nuh_extban, which
-    will deal checking a chained extban (including checking for restricted extbans),
+    will deal checking a stacked extban (including checking for restricted extbans),
     or it can call that function from its own is_ok routine. For the latter case,
     remember to pass only the mask part of your ban format (ie, don't just pass para as
     otherwise it'll just call your is_ok again).
   - For conv_param function, the extban can either assign extban_conv_param_nuh_or_extban,
-    which will automatically call conv_param for a chained extban, or pretty up a n!u@h mask.
+    which will automatically call conv_param for a stacked extban, or pretty up a n!u@h mask.
   - For is_banned, the extban should call ban_check_mask with the mask part of the parameter.
     This will automatically call is_banned for a stacked extban, or match against a n!u@h. n!u@h
     is checked against the current user (ie, with the info in the globals ban_ip, etc), so things
     can get weird if you call this outside a normal ban check.
-  Modules must keep in mind that chained extban support is not available (and neither are the three
+  Modules must keep in mind that stacked extban support is not available (and neither are the three
   functions above) if DISABLE_STACKED_EXTBANS is #defined (this is controled by Config). Modules will
   not compile/load if they try to use them anyway.
   This change should not break extban modules, and should need some more extensive testing.
-- Misc fix for disabling extban chains, should've done stuff in our autoconf
+- Misc fix for disabling stacked extbans, should've done stuff in our autoconf
   stuff instead of hacking configure directly :P .
 - Made the timesynch log output more clear and understandable.
 - Added an 'UnrealIRCd started' log message on startup.
@@ -1970,7 +1970,7 @@
 - ./Config now remembers extra/custom ./configure parameters.
 - Fixed bug in CVS where the ban exempt (+e) handling was reversed: if a
   non-matching +e was present, one could walk through bans. Reported by
-  tabrisnet (#0003909). Bug was caused by chained/stacked extbans.
+  tabrisnet (#0003909). Bug was caused by stacked extbans.
 - Partially fixed bug where IPv4 addresses were randomly mishandled by the
   cgiirc code, resulting in the sockhost/hostmask being set to something like
   ::ffff:127.0.0.1, which confused the s2s protocol. Reported by tabrisnet
@@ -2068,3 +2068,4 @@
 - Force compilation with bundled c-ares to statically link using more
   sed hackery in configure.ac.
 - Remove extras/c-ares before each time c-ares is compiled.
+- Uniform naming for 'stacked extbans' in Changelog/etc.