From b8084b8d088764f985b2fa57a22d6207673eaa19 Mon Sep 17 00:00:00 2001 From: Aliaksei Urbanski Date: Fri, 15 Dec 2023 00:37:56 +0300 Subject: [PATCH] Update Read the Docs name and URL (#3588) --- README.rst | 6 +++--- peps/pep-0426.rst | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.rst b/README.rst index 9a97a904c..096ae335c 100644 --- a/README.rst +++ b/README.rst @@ -34,11 +34,11 @@ generation to fail, or result in major rendering defects relative to what you intend. -Browse the ReadTheDocs preview ------------------------------- +Browse the "Read the Docs" preview +---------------------------------- For every PR, we automatically create a preview of the rendered PEPs using -`ReadTheDocs `_. +`Read the Docs `_. You can find it in the merge box at the bottom of the PR page: 1. Click "Show all checks" to expand the checks section diff --git a/peps/pep-0426.rst b/peps/pep-0426.rst index 6653ecdba..84b72a68c 100644 --- a/peps/pep-0426.rst +++ b/peps/pep-0426.rst @@ -1111,7 +1111,7 @@ RPM. A documentation toolchain dependency like Sphinx would either go in the ``build`` extra (for example, if man pages were included in the built distribution) or in the ``doc`` extra (for example, if the -documentation is published solely through ReadTheDocs or the +documentation is published solely through Read the Docs or the project website). This would be enough to allow an automated converter to map it to an appropriate dependency in the spec file.