Improve docs formatting

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/en/usage.rst b/doc/en/usage.rst
index 9da5d3fce..e13ff24c7 100644
--- a/doc/en/usage.rst
+++ b/doc/en/usage.rst
@@ -198,10 +198,10 @@ Using the builtin breakpoint function
 Python 3.7 introduces a builtin ``breakpoint()`` function. 
 Pytest supports the use of ``breakpoint()`` with the following behaviours:
 
- - When breakpoint() is called and PYTHONBREAKPOINT is set to the default value, PyTest will use the Custom PDB trace UI instead of the system default Pdb.
- - When tests are complete, the system will default back to the system Pdb trace UI.
- - If --pdb is called on execution of Pytest, the custom Pdb interface is used on bothbreakpoint() and failed tests/unhandled exceptions.
- - If --pdbcls is used, the custom class will be executed when a test fails (as expected within existing behaviour), but also when breakpoint() is called from within a test, the custom class debugger will be instantiated.
+ - When ``breakpoint()`` is called and ``PYTHONBREAKPOINT`` is set to the default value, pytest will use the custom internal PDB trace UI instead of the system default ``Pdb``.
+ - When tests are complete, the system will default back to the system ``Pdb`` trace UI.
+ - If ``--pdb`` is called on execution of pytest, the custom internal Pdb trace UI is used on ``bothbreakpoint()`` and failed tests/unhandled exceptions.
+ - If ``--pdbcls`` is used, the custom class debugger will be executed when a test fails (as expected within existing behaviour), but also when ``breakpoint()`` is called from within a test, the custom class debugger will be instantiated.
 
 .. _durations: