diff options
author | Nicholas Chin <nic.c3.14@gmail.com> | 2022-08-23 17:51:21 -0600 |
---|---|---|
committer | Felix Held <felix-coreboot@felixheld.de> | 2022-08-29 14:26:07 +0000 |
commit | c39598c975a7166d6a426087170e2477f056344c (patch) | |
tree | a01f06ddebf33bee7eb334f570669ef625fccaaa | |
parent | 3f6de867e891464c9f5dd22aea2247d5dc86d5e9 (diff) |
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 <nic.c3.14@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/67000
Reviewed-by: Felix Singer <felixsinger@posteo.net>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
-rw-r--r-- | Documentation/tutorial/part3.md | 8 |
1 files 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 |