modxorg · Ibochkarev · Aug 15, 2026
diff --git a/en/building-sites/settings/tvs_below_content.md b/en/building-sites/settings/tvs_below_content.md
@@ -14,7 +14,7 @@ This controls whether Template Variables show up on their own tab or below resou
 
 ### Yes
 
-All TVs appear below the Resource content, just like they did for MODX Evolution.
+All TVs appear below the Resource content.
 
 ![](tvs_below_content.jpg)
 

diff --git a/en/building-sites/tag-syntax/output-filters/index.md b/en/building-sites/tag-syntax/output-filters/index.md
@@ -12,7 +12,7 @@ Filters in Revolution allow you to manipulate the way data is presented or parse
 
 ## Output Filter
 
-In Revolution, the Output Filter applies one or more of series of output modifiers, which behave similarly to PHx calls in MODX Evolution - except they're built into the core. The syntax looks like this:
+An Output Filter applies one or more output modifiers built into the core. The syntax looks like this:
 
 ```php
 [[element:modifier=`value`]]

diff --git a/en/contribute/issues.md b/en/contribute/issues.md
@@ -78,8 +78,8 @@ Please file issues for the appropriate project in the issues section at Github:
 
 Issues that the community can initiate or collaborate on include:
 
-- bugs in MODX (Evolution and Revolution) and some Extras
-- feature requests for MODX (Evolution and Revolution) and some Extras
+- bugs in MODX and some Extras
+- feature requests for MODX and some Extras
 - reports of bugs or problems with various MODX websites or parts thereof
 
 Many feature requests and bug reports stem originally from discussions in the forums. If you are filing a bug report or feature request for which there is forum discussion, please include a link to the forum thread.

diff --git a/en/extending-modx/custom-manager-pages/index.md b/en/extending-modx/custom-manager-pages/index.md
@@ -10,8 +10,6 @@ CMP stands for Custom Manager Page, and it is simply a custom page that loads in
 
 If you are a developer looking to build an extra which includes a component, you should follow the [Developing an Extra for MODX Revolution tutorial](extending-modx/tutorials/developing-an-extra), as it walks you through all the specific steps and terminology based on an example package called doodles. This page only goes into a minimum set up for custom manager pages.
 
-The equivalent of a CMP or Component in MODX Evolution is a Module, though the technique in which they are created is quite different.
-
 ## Namespaces
 
 CMPs need a namespace in order for MODX to know where to load the files from.

diff --git a/en/extending-modx/getting-started/tutorial/index.md b/en/extending-modx/getting-started/tutorial/index.md
@@ -4,7 +4,7 @@ _old_id: "1116"
 _old_uri: "2.x/case-studies-and-tutorials/php-coding-in-modx-revolution,-pt.-i"
 ---
 
-So, a lot of people have been asking about the new codebase. Is it coder-friendly? Will it be a big deviation from 0.9.6/Evolution? Does it support OOP projects? Is it faster? Will it be easy to learn?
+So, a lot of people have been asking about the codebase. Is it coder-friendly? Does it support OOP projects? Is it faster? Will it be easy to learn?
 
 In these tutorials, we plan to answer those questions with YES.
 

diff --git a/en/extending-modx/menus/action-list.md b/en/extending-modx/menus/action-list.md
@@ -10,7 +10,7 @@ _old_uri: "2.x/developing-in-modx/advanced-development/custom-manager-pages/acti
 
 Within the Manager, you can access a list of actions with the `MODx.action` variable. Do NOT rely on any list with manager action IDs as these IDs are not hardcoded in the MODX Core, but instead they are dynamically created during setup and just happen to have a certain ID.
 
-Back in Evolution there was indeed a fixed list, but there has never been one in Revolution.
+There has never been a fixed list of manager actions in modern MODX.
 
 ### Before Revolution 2.3
 

diff --git a/en/extras/advsearch/index.md b/en/extras/advsearch/index.md
@@ -20,7 +20,7 @@ MySQL-only search (`&engine=` `mysql`, the default) does not need ZendSearch.
 
 ## History
 
-AdvSearch was written by [Coroico](https://github.com/coroico) and first released on August 14th, 2011. It is loosely based on AjaxSearch for MODX Evolution by KyleJ/Coroico, with optional Lucene indexing via ZendSearch.
+AdvSearch was written by [Coroico](https://github.com/coroico) and first released on August 14th, 2011. It is loosely based on AjaxSearch by KyleJ/Coroico, with optional Lucene indexing via ZendSearch.
 
 ### Download
 

diff --git a/en/extras/ajaxupload/index.md b/en/extras/ajaxupload/index.md
@@ -18,7 +18,7 @@ With two Formit hooks the upload queue could be pre filled from Formit field val
 
 ## History & Info
 
-AjaxUpload was initially written in 2012 for MODX Evolution and is maintained and developed since then by [Thomas Jakobi](https://github.com/jako).
+AjaxUpload was first released in 2012 and is maintained by [Thomas Jakobi](https://github.com/jako).
 
 ### Download
 

diff --git a/en/extras/breadcrumbs/index.md b/en/extras/breadcrumbs/index.md
@@ -15,7 +15,7 @@ Breadcrumbs is a simple navigation trail [Snippet](developing-in-modx/basic-deve
 
 ## History
 
-Breadcrumbs has been around since the start of MODX 0.9.1, or MODX Evolution, with its first release on June 30th, 2006. It has had many different authors since its inception.
+Breadcrumbs has been around since MODX 0.9.1, with its first release on June 30th, 2006. It has had many different authors since its inception.
 
 ### Public Releases
 
@@ -26,14 +26,14 @@ Breadcrumbs has been around since the start of MODX 0.9.1, or MODX Evolution, wi
 | 1.1-beta1  | May 21st, 2009      | splittingred | Revolution |
 | 1.0-alpha4 | April 21st, 2009    | splittingred | Revolution |
 | 1.0-alpha3 | March 24th, 2009    | splittingred | Revolution |
-| 1.0.1      | April 25th, 2008    | jaredc       | Evolution  |
-| 1.0.0      | April 22nd, 2008    | jaredc       | Evolution  |
-| 0.9g       | March 26th, 2008    | webe         | Evolution  |
-| 0.9f       | January 17th, 2008  | jaredc       | Evolution  |
-| 0.9e       | January 11th, 2008  | jaredc       | Evolution  |
-| 0.9d       | July 12th, 2006     | jaredc       | Evolution  |
-| 0.91       | July 10th, 2006     | tillda       | Evolution  |
-| 0.9c       | June 30th, 2006     | jaredc       | Evolution  |
+| 1.0.1      | April 25th, 2008    | jaredc       | 1.x        |
+| 1.0.0      | April 22nd, 2008    | jaredc       | 1.x        |
+| 0.9g       | March 26th, 2008    | webe         | 1.x        |
+| 0.9f       | January 17th, 2008  | jaredc       | 1.x        |
+| 0.9e       | January 11th, 2008  | jaredc       | 1.x        |
+| 0.9d       | July 12th, 2006     | jaredc       | 1.x        |
+| 0.91       | July 10th, 2006     | tillda       | 1.x        |
+| 0.9c       | June 30th, 2006     | jaredc       | 1.x        |
 
 ### Download
 

diff --git a/en/extras/filedownload-r/index.md b/en/extras/filedownload-r/index.md
@@ -11,7 +11,7 @@ This way, the full url of the file will not be revealed and the files/directorie
 Each file can also be assigned a download counter, which is stored in a custom database table.
 
 The FileDownloadR project was started in 2011 by [Rico Goldsky](https://github.com/goldsky) as a rewite of the 
-FileDownload Evolution package by Kyle Jaebker. It is maintained since 2023 by [Thomas Jakobi](https://github.com/Jako).
+Based on the earlier FileDownload package by Kyle Jaebker. Maintained since 2023 by [Thomas Jakobi](https://github.com/Jako).
 
 FileDownloadR can be installed from within the MODX Revolution manager via Package Management, or from the MODX Extras 
 Repository, available on [modx.com/extras/package/filedownloadr](https://modx.com/extras/package/filedownloadr)

diff --git a/en/extras/fileupload/index.md b/en/extras/fileupload/index.md
@@ -20,7 +20,7 @@ FileUpload presents a file upload form.
 - Downloads: 5,348
 - License: Free
 - [Discuss Extra](http://www.modxcms.com/forums/index.php?topic=5889)
-- Requires: Evolution 1.0.x or greater
+- Requires: MODX 2.x or greater
 - Supports: mysql
 
 ## History

diff --git a/en/extras/firstchildredirect/index.md b/en/extras/firstchildredirect/index.md
@@ -4,14 +4,12 @@ _old_id: "641"
 _old_uri: "revo/firstchildredirect"
 ---
 
-FirstChildRedirect is a snippet that will redirect a certain resource to its first child resource. There is a version for both Revolution and Evolution, of which the Revolution one allows more easy customization.
+FirstChildRedirect is a snippet that redirects a resource to its first child resource.
 
 ## Installation & bugs
 
 FirstChildRedirect can be installed through the MODX Revolution Package Manager, or installed manually by downloading the package from the MODX Extras website, uploading it to core/packages and adding a new package through the package manager from a local search.
 
-FirstChildRedirect is also available for MODX Evolution, however that does not support all additional parameters as described below.
-
 ## Snippet usage
 
 The snippet is really easy to use, just call uncached it in the content or template of the container resource you want to redirect to its first child.
@@ -22,10 +20,10 @@ The snippet is really easy to use, just call uncached it in the content or templ
 
 Alternatively, you can specify one or more parameters in the snippet call which influence how the redirect will be handled.
 
-| Parameter     | Evo/Revo | Details                                                                                                                                                                                                                                                                                                                                                                                                                                        | Default                            |
+| Parameter     | Optional | Details                                                                                                                                                                                                                                                                                                                                                                                                                                        | Default                            |
 | ------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
 | &docid        | Yes/Yes  | Setting a docid parameter to another resource's ID will tell the snippet to use that resource as the container to look in for the first child.                                                                                                                                                                                                                                                                                                 | current resource ID (ie `[[*id]]`) |
-| &default      | No\*/Yes | The resource to redirect to when there are no children resources found. This can be either a resource ID or one of the following settings: site\_start, site\_unavailable\_page, error\_page or unauthorized\_page. \* In Evolution, this also defaults to site\_start and can be modified in the actual snippet code if required. Just find $modx->config\['site\_start'\] and replace that by an ID or one of the system settings mentioned. | site\_start setting                |
+| &default      | No\*/Yes | The resource to redirect to when there are no children resources found. This can be either a resource ID or one of the following settings: site\_start, site\_unavailable\_page, error\_page or unauthorized\_page. | site\_start setting                |
 | &sortBy       | No/Yes   | Any valid resource fieldname to sort the children found on.                                                                                                                                                                                                                                                                                                                                                                                    | menuindex setting                  |
 | &sortDir      | No/Yes   | Either 'desc' for descending (redirects to highest menuindex or &sortBy field found) or 'asc' for ascending (redirects to lowest menuindex or &sortBy field found).                                                                                                                                                                                                                                                                            | "asc"                              |
 | &responseCode | No/Yes   | The response code (status code) for sending the redirect. Defaults to a 301 ("HTTP/1.1 301 Moved Permanently") but also contains shortcuts for 302 (temporarily) - you can also specify the complete response code (including the HTTP part and name) for others. _Added in 2.3.1._                                                                                                                                                            | 301                                |

diff --git a/en/extras/formit/index.md b/en/extras/formit/index.md
@@ -34,7 +34,7 @@ As of FormIt 1.1.4, all fields will automatically have `stripTags` applied. To a
 
 ## How to Use
 
-Simply place the FormIt snippet call into the Resource that contains the form you want to use. Unlike similar predecessors (most notably eForm in MODX Evolution), you do not put the form into a Chunk and reference the Chunk in the FormIt snippet call: you literally put the snippet call along side the form you want it to process. Specify the "hooks" (or post-validation processing scripts) in the snippet call. Then add validation via the _&validate_ and _&customValidators_ parameters in the snippet tag.
+Simply place the FormIt snippet call into the Resource that contains the form you want to use. Place the snippet call next to the form you want it to process. Do not put the form into a Chunk and reference that Chunk from the FormIt call. Specify the "hooks" (or post-validation processing scripts) in the snippet call. Then add validation via the _&validate_ and _&customValidators_ parameters in the snippet tag.
 
 If you have multiple forms on a page, set the _&submitVar_ property on your Snippet call to a name of a form element within the form (ie, ``&submitVar=`form1-submit` ``). This tells FormIt to only process form requests with that POST variable. Multiple forms should be used with INPUT type="submit" name="form1-submit", button elements have been reported not working.
 

diff --git a/en/extras/getdynadescription/index.md b/en/extras/getdynadescription/index.md
@@ -6,7 +6,7 @@ _old_uri: "revo/getdynadescription"
 
 ## What is getDynaDescription?
 
-Conversion and rewrite of the Evolution getDynaDescription snippet.
+Conversion and rewrite of the earlier getDynaDescription snippet.
 
 Creates Meta tags from a TV, the resource description field, or the resource content field.
 

diff --git a/en/extras/getresources/index.md b/en/extras/getresources/index.md
@@ -21,7 +21,7 @@ getResources was first written by Jason Coward (opengeek) and released on June 3
 
 It can be downloaded from within the MODX Revolution manager via [Package Management](developing-in-modx/advanced-development/package-management "Package Management"), or from the MODX Extras Repository, here: <https://modx.com/extras/package/getresources>
 
-It is NOT a replacement for Ditto, but rather an alternative component that can accomplish some of the things that the more specialized components do, i.e. Ditto, Wayfinder, Breadcrumbs; basically anything that output the properties for a list of Resources (formerly Documents in MODX Evolution).
+It is NOT a replacement for Ditto, but rather an alternative component that can accomplish some of the things that the more specialized components do, i.e. Ditto, Wayfinder, Breadcrumbs; basically anything that outputs the properties for a list of Resources.
 
 Documentation and tutorials on Russian can be found here: <http://modx.by/docs/modx-add-ons/getresources/>
 

diff --git a/en/extras/gorevo/index.md b/en/extras/gorevo/index.md
@@ -6,7 +6,7 @@ _old_uri: "revo/gorevo"
 
 ## What is GoRevo?
 
-GoRevo is a commercial extra that performs an intelligent migration of MODX Evolution sites to MODX Revolution. 
+GoRevo is a commercial Extra that migrates older 1.x sites to modern MODX. 
 
 ### Features
 
@@ -25,15 +25,15 @@ GoRevo is a commercial extra that performs an intelligent migration of MODX Evol
 - Custom Plugins
 - Selected files and/or directories
 
-GoRevo will attempt to convert Ditto, Breadcrumbs, WebLogin, WebLoginPE, and PHX tags to work in Revolution. Wayfinder tags will generally work as is. GoRevo will also attempt to duplicate the User Groups, User Login credentials, and Resource Groups from the Evolution site.
+GoRevo attempts to convert Ditto, Breadcrumbs, WebLogin, WebLoginPE, and PHX tags for modern MODX. Wayfinder tags usually work as-is. GoRevo also tries to duplicate User Groups, login credentials, and Resource Groups from the source site.
 
 You can get more information about GoRevo at [Bob's Guides](https://bobsguides.com/why-choose-gorevo.html).
 
 ## History
 
 - Author: Bob Ray [Bob's Guides](https://bobsguides.com)
 
-GoRevo took about six months of intensive development. It has been used to convert many Evolution sites to MODX Revolution, including many conversions performed by MODX LLC.
+GoRevo took about six months of intensive development. Teams have used it to convert many older 1.x sites to modern MODX, including conversions performed by MODX LLC.
 
 This version of the GoRevo extra was developed by Bob Ray in 2014. As of Jun 22, 2017 it had been last updated on December 21, 2017, had 190 commits, and had been downloaded 61 times. The GoRevo package consists of 1,563 separate files, containing 32,211 lines of code.
 

diff --git a/en/extras/index.md b/en/extras/index.md
@@ -102,7 +102,6 @@ This does not mean however that these are your only options. Browse the reposito
 ### Upgrading MODX
 
 - [UpgradeMODX](https://bobsguides.com/upgrade-modx-package.html) allows you to upgrade MODX Revolution from within the MODX Manager.
-- [GoRevo](https://bobsguides.com/why-choose-gorevo.html) (premium extra from Bob Ray) provides a tool for migrating from MODX Evolution to MODX Revolution.
 
 ## Distributing your own Extras
 

diff --git a/en/extras/metax/index.md b/en/extras/metax/index.md
@@ -13,7 +13,7 @@ Requirements
 
 ## History
 
-MetaX was created in 2010 for both MODX Evolution and later MODX Revolution using the same codebase. Since then, the codebase for MetaX has been split to take better advantage of new features in MODX Revolution. All versions of MetaX have been released by it's creator, Sal Sodano ( <http://salscode.com>), with other contributors along the way.
+MetaX was created in 2010. Later builds target MODX Revolution features. All versions of MetaX have been released by its creator, Sal Sodano (<http://salscode.com>), with other contributors along the way.
 
 ### Development
-Original file line number
+Diff line change
@@ Expand Up @@
     ### Yes
-    All TVs appear below the Resource content, just like they did for MODX Evolution.
+    All TVs appear below the Resource content.
     ![](tvs_below_content.jpg)
@@ Expand Down @@