From a3d3a813baf1c88126525e52696b3a97155c451c Mon Sep 17 00:00:00 2001
From: Brett Cannon <brett@python.org>
Date: Thu, 4 Jan 2024 11:21:44 -0800
Subject: [PATCH] Remove the explicit list of PaaS platforms

It can be misconstrued as an endorsement and we can't keep up w/ all PaaS platforms which support Python to make the list comprehensive/impartial.
---
 source/overview.rst | 20 ++++++--------------
 1 file changed, 6 insertions(+), 14 deletions(-)

diff --git a/source/overview.rst b/source/overview.rst
index 3627e8122..8c68036a7 100644
--- a/source/overview.rst
+++ b/source/overview.rst
@@ -195,20 +195,12 @@ hood, you can always read the sections beyond.
 Service platforms
 *****************
 
-If you're developing for a "Platform-as-a-Service" or "PaaS" like
-Heroku or Google App Engine, you are going to want to follow their
-respective packaging guides.
-
-* `Heroku <https://devcenter.heroku.com/articles/getting-started-with-python>`_
-* `Google App Engine <https://cloud.google.com/appengine/docs/python/>`_
-* `PythonAnywhere <https://www.pythonanywhere.com/>`_
-* `OpenShift <https://blog.openshift.com/getting-started-python/>`_
-* "Serverless" frameworks like :gh:`Zappa <zappa/Zappa>`
-
-In all these setups, the platform takes care of packaging and
-deployment, as long as you follow their patterns. Most software does
-not fit one of these templates, hence the existence of all the other
-options below.
+If you're developing for a
+"`Platform-as-a-Service <https://en.wikipedia.org/wiki/Platform_as_a_service>`_"
+or "PaaS", you are going to want to follow their respective packaging
+guides. These types of platforms take care of packaging and deployment,
+as long as you follow their patterns. Most software does not fit one of
+these templates, hence the existence of all the other options below.
 
 If you're developing software that will be deployed to machines you
 own, users' personal computers, or any other arrangement, read on.