matplotlib
diff --git a/‎doc/api/api_changes.rst
Lines changed: 1 addition & 1 deletion b/‎doc/api/api_changes.rst
Lines changed: 1 addition & 1 deletion
diff --git a/‎doc/api/api_changes_3.3/2019-04-25-AL.rst renamed to ‎doc/api/recent_api_changes_3.3/2019-04-25-AL.rst b/‎doc/api/api_changes_3.3/2019-04-25-AL.rst renamed to ‎doc/api/recent_api_changes_3.3/2019-04-25-AL.rst
diff --git a/‎doc/api/api_changes_3.3/README.rst renamed to ‎doc/api/recent_api_changes_3.3/README.rst
Lines changed: 1 addition & 1 deletion b/‎doc/api/api_changes_3.3/README.rst renamed to ‎doc/api/recent_api_changes_3.3/README.rst
Lines changed: 1 addition & 1 deletion
diff --git a/‎doc/api/api_changes_3.3/behaviour.rst renamed to ‎doc/api/recent_api_changes_3.3/behaviour.rst b/‎doc/api/api_changes_3.3/behaviour.rst renamed to ‎doc/api/recent_api_changes_3.3/behaviour.rst
diff --git a/‎doc/api/api_changes_3.3/deprecations.rst renamed to ‎doc/api/recent_api_changes_3.3/deprecations.rst b/‎doc/api/api_changes_3.3/deprecations.rst renamed to ‎doc/api/recent_api_changes_3.3/deprecations.rst
diff --git a/‎doc/api/api_changes_3.3/development.rst renamed to ‎doc/api/recent_api_changes_3.3/development.rst b/‎doc/api/api_changes_3.3/development.rst renamed to ‎doc/api/recent_api_changes_3.3/development.rst
diff --git a/‎doc/api/api_changes_3.3/removals.rst renamed to ‎doc/api/recent_api_changes_3.3/removals.rst b/‎doc/api/api_changes_3.3/removals.rst renamed to ‎doc/api/recent_api_changes_3.3/removals.rst
diff --git a/‎doc/devel/coding_guide.rst
Lines changed: 2 additions & 2 deletions b/‎doc/devel/coding_guide.rst
Lines changed: 2 additions & 2 deletions
diff --git a/‎doc/devel/contributing.rst
Lines changed: 1 addition & 1 deletion b/‎doc/devel/contributing.rst
Lines changed: 1 addition & 1 deletion
diff --git a/‎doc/devel/release_guide.rst
Lines changed: 1 addition & 1 deletion b/‎doc/devel/release_guide.rst
Lines changed: 1 addition & 1 deletion
@@ -21,7 +21,7 @@ added to Matplotlib, see :ref:`whats-new`.
    .. note::
 
       The list below is a table of contents of individual files from the
-      'api_changes_3.3' folder.
+      'recent_api_changes_3.3' folder.
 
       When a release is made
 
 
@@ -4,7 +4,7 @@ Adding API change notes
 =======================
 
 API change notes for future releases are collected in the directory
-:file:`api_changes_3.3`. They are divided into four categories:
+:file:`recent_api_changes_3.3`. They are divided into four categories:
 
 - **Deprecations**: Announcements of future changes. Typically, these will
   raise a deprecation warning and users of this API should change their code
 
@@ -95,7 +95,7 @@ Documentation
   :file:`doc/users/whats_new.rst`.
 
 * If you change the API in a backward-incompatible way, please
-  document it in the relevant file in :file:`doc/api/api_changes_3.3`.
+  document it in the relevant file in :file:`doc/api/recent_api_changes_3.3`.
 
 .. _pr-labels:
 
@@ -145,7 +145,7 @@ Merging
   the PR.
 
   Ensure that all API changes are documented in the relevant file in
-  :file:`doc/api/api_changes_3.3` and significant new features have and
+  :file:`doc/api/recent_api_changes_3.3` and significant new features have and
   entry in :file:`doc/user/whats_new`.
 
   - If a PR already has a positive review, a core developer (e.g. the first
 
@@ -318,7 +318,7 @@ Changes to the public API must follow a standard deprecation procedure to
 prevent unexpected breaking of code that uses Matplotlib.
 
 - Deprecations must be announced via an entry in
-  :file:`doc/api/api_changes_3.3`.
+  :file:`doc/api/recent_api_changes_3.3`.
 - Deprecations are targeted at the next point-release (i.e. 3.x.0).
 - The deprecated API should, to the maximum extent possible, remain fully
   functional during the deprecation period. In cases where this is not
 
@@ -112,7 +112,7 @@ For the "what's new",
 Similarly for the "API changes",
 
  1. copy the current api changes to a file is :file:`doc/api/prev_api_changes`
- 2. merge all of the files in :file:`doc/api/api_changes_3.3/` into
+ 2. merge all of the files in :file:`doc/api/recent_api_changes_3.3/` into
     :file:`doc//whats_new.rst`
  3. comment out the next API changes at the top.