From 84d89969fb9c88eabac6676e7b8852e9c48db427 Mon Sep 17 00:00:00 2001
From: aizpurua23a <57321880+aizpurua23a@users.noreply.github.com>
Date: Tue, 26 Jul 2022 21:28:19 +0200
Subject: [PATCH] Edit fixtures.rst to not modify previous lines.

---
 doc/en/how-to/fixtures.rst | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/doc/en/how-to/fixtures.rst b/doc/en/how-to/fixtures.rst
index 9498442c8..899474b88 100644
--- a/doc/en/how-to/fixtures.rst
+++ b/doc/en/how-to/fixtures.rst
@@ -680,8 +680,6 @@ So to make sure we don't run the finalizer code when we wouldn't need to, we
 would only add the finalizer once the fixture would have done something that
 we'd need to teardown.
 
-Here's how the previous example would look using the ``addfinalizer`` method:
-
 .. code-block:: python
 
     # content of test_emaillib.py
@@ -730,8 +728,8 @@ Here's how the previous example would look using the ``addfinalizer`` method:
 
 
 Here's how the previous example would look using the ``addfinalizer`` method:
- It's a bit longer than yield fixtures and a bit more complex, but it
- does offer some nuances for when you're in a pinch.
+It's a bit longer than yield fixtures and a bit more complex, but it
+does offer some nuances for when you're in a pinch.
 
 Note on finalizer order
 """"""""""""""""""""""""