bpo-32910: Remove implementation detail in venv documentation. (GH-14968)
(cherry picked from commit 91e49575095ca16d1b67dd8822deeb7885e421da)
Co-authored-by: Derek Keeler <d3r3kk@users.noreply.github.com>
diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc
index af30cbb..1b24721 100644
--- a/Doc/using/venv-create.inc
+++ b/Doc/using/venv-create.inc
@@ -118,10 +118,8 @@
and run with the virtual environment's Python automatically.
You can deactivate a virtual environment by typing "deactivate" in your shell.
-The exact mechanism is platform-specific: for example, the Bash activation
-script defines a "deactivate" function, whereas on Windows there are separate
-scripts called ``deactivate.bat`` and ``Deactivate.ps1`` which are installed
-when the virtual environment is created.
+The exact mechanism is platform-specific and is an internal implementation
+detail (typically a script or shell function will be used).
.. versionadded:: 3.4
``fish`` and ``csh`` activation scripts.