rename asciidoc-python.adoc to asciidoc-py and use AsciiDoc.py to refer to original processor

4 files changed, 5 insertions, 5 deletions

diff --git a/docs/modules/ROOT/pages/converters.adoc b/docs/modules/ROOT/pages/converters.adoc
index 31c54489..d46e8a7d 100644
--- a/docs/modules/ROOT/pages/converters.adoc
+++ b/docs/modules/ROOT/pages/converters.adoc
@@ -88,7 +88,7 @@ The tool provides built-in theming via a YAML configuration file, which is docum
 TIP: Asciidoctor PDF is the preferred tool for converting to PDF and is fully supported by the Asciidoctor community.
 
 a2x::
-A DocBook toolchain frontend provided by that AsciiDoc Python project.
+A DocBook toolchain frontend provided by that AsciiDoc.py project.
 +
 To use this tool, you should first convert to DocBook using Asciidoctor, then convert the DocBook to PDF using a2x.
 a2x accepts a DocBook file as input and can convert it to a PDF using either Apache FOP or dblatex.
diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc
index 0644b608..d74c563f 100644
--- a/docs/modules/ROOT/pages/index.adoc
+++ b/docs/modules/ROOT/pages/index.adoc
@@ -18,8 +18,8 @@ Asciidoctor is also distributed as a package for numerous Linux distributions as
 
 Asciidoctor is open source software that is available under the terms of the MIT license and {url-org}[hosted on GitHub^].
 
-Asciidoctor is the successor to AsciiDoc Python (AsciiDoc.py).
-If you're using AsciiDoc.py, follow xref:migrate:asciidoc-python.adoc[] to learn how to upgrade to Asciidoctor.
+Asciidoctor is the successor to AsciiDoc.py (aka AsciiDoc Python).
+If you're using AsciiDoc.py, follow xref:migrate:asciidoc-py.adoc[] to learn how to upgrade to Asciidoctor.
 
 == Basic usage
 
diff --git a/docs/modules/ROOT/pages/localization-support.adoc b/docs/modules/ROOT/pages/localization-support.adoc
index 5a357f33..cf2d0bc0 100644
--- a/docs/modules/ROOT/pages/localization-support.adoc
+++ b/docs/modules/ROOT/pages/localization-support.adoc
@@ -18,7 +18,7 @@ See {url-org}/asciidoctor/issues/1601[issue #1601^] for details.
 In the interim, you can leverage the DocBook toolchain to get right-to-left support.
 * Attributes that store dates and times (e.g., `docdatetime`) are always formatted like `2019-01-04 19:26:06 GMT+0000`.
 * Message (aka logging) strings are always in English.
-* Asciidoctor does not support the language conf files used by AsciiDoc Python.
+* Asciidoctor does not support the language conf files used by AsciiDoc.py.
 However, Asciidoctor does provide {url-lang-attributes}[a translation file^] that can be used for a similar purpose.
 
 [#customizing-labels]
diff --git a/docs/modules/ROOT/pages/whats-new.adoc b/docs/modules/ROOT/pages/whats-new.adoc
index 7c7b2305..7a0c6384 100644
--- a/docs/modules/ROOT/pages/whats-new.adoc
+++ b/docs/modules/ROOT/pages/whats-new.adoc
@@ -389,7 +389,7 @@ _**Release date:** 2019.03.22_
 == Build and infrastructure
 
 * clear SOURCE_DATE_EPOCH env var when testing timezones (PR #2969) (*@aerostitch*)
-* remove compat folder (removes the AsciiDoc Python config file that provides pseudo-compliance with Asciidoctor and a stylesheet for an old Font Awesome migration)
+* remove compat folder (removes the AsciiDoc.py config file that provides pseudo-compliance with Asciidoctor and a stylesheet for an old Font Awesome migration)
 * add Ruby 2.6.0 to build matrix
 * stop running CI job on unsupported versions of Ruby
 * exclude test suite, build script, and Gemfile from gem (#3044)