[Python-checkins] bpo-28546: [doc] Clarify setting pdb breakpoints (GH-30360)

[miss-islington]

https://github.com/python/cpython/commit/a74eb5465582dd6e194a84ce4c66c12453373304
commit: a74eb5465582dd6e194a84ce4c66c12453373304
branch: 3.9
author: Miss Islington (bot) <31488909+miss-islington at users.noreply.github.com>
committer: miss-islington <31488909+miss-islington at users.noreply.github.com>
date: 2022-01-07T12:06:43-08:00
summary:

bpo-28546: [doc] Clarify setting pdb breakpoints (GH-30360)


Co-authored-by: Ian Kelling <ian at iankelling.org>
(cherry picked from commit 6d07a9fb7cb31433c376a1aa20ea32001da0a418)

Co-authored-by: Hugo van Kemenade <hugovk at users.noreply.github.com>

files:
M Doc/library/pdb.rst

diff --git a/Doc/library/pdb.rst b/Doc/library/pdb.rst
index ed1e9712c0e3d..13e1a1993692d 100644
--- a/Doc/library/pdb.rst
+++ b/Doc/library/pdb.rst
@@ -67,14 +67,13 @@ useful than quitting the debugger upon program's exit.
    before the first line of the module.
 
 
-The typical usage to break into the debugger from a running program is to
-insert ::
+The typical usage to break into the debugger is to insert::
 
    import pdb; pdb.set_trace()
 
-at the location you want to break into the debugger.  You can then step through
-the code following this statement, and continue running without the debugger
-using the :pdbcmd:`continue` command.
+at the location you want to break into the debugger, and then run the program.
+You can then step through the code following this statement, and continue
+running without the debugger using the :pdbcmd:`continue` command.
 
 .. versionadded:: 3.7
    The built-in :func:`breakpoint()`, when called with defaults, can be used