From c39598c975a7166d6a426087170e2477f056344c Mon Sep 17 00:00:00 2001 From: Nicholas Chin Date: Tue, 23 Aug 2022 17:51:21 -0600 Subject: [PATCH] Documentation/tutorial: Fix markdown heading in Part 3 Part of the content was on the same line as the heading. Change-Id: Ia19487d80e9f004d59f96ff09e1f3de4f37c2f77 Signed-off-by: Nicholas Chin Reviewed-on: https://review.coreboot.org/c/coreboot/+/67000 Reviewed-by: Felix Singer Tested-by: build bot (Jenkins) --- Documentation/tutorial/part3.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/tutorial/part3.md b/Documentation/tutorial/part3.md index 83b34088c3..ff07ece367 100644 --- a/Documentation/tutorial/part3.md +++ b/Documentation/tutorial/part3.md @@ -23,10 +23,10 @@ though TDD has a different work flow of building tests first, followed by the code that satisfies them, the process of writing tests and adding them to the tree is the same. -## Analysis of unit under test First of all, it is necessary to -precisely establish what we want to test in a particular module. Usually -this will be an externally exposed API, which can be used by other -modules. +## Analysis of unit under test +First of all, it is necessary to precisely establish what we want to +test in a particular module. Usually this will be an externally exposed +API, which can be used by other modules. ```eval_rst .. admonition:: i2c-test example