bpo-32910: Remove implementation detail in venv documentation. (GH-14968)

(cherry picked from commit 91e4957)

Co-authored-by: Derek Keeler <[email protected]>

Author: miss-islington

Doc/using/venv-create.inc

@@ -118,10 +118,8 @@ installed in a virtual environment should be runnable without activating it,
 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.

Misc/NEWS.d/next/Documentation/2019-07-25-10-30-32.bpo-32910.caLLAe.rst

@@ -0,0 +1 @@
+Remove implementation-specific behaviour of how venv's Deactivate works.