sravan/system76-coreboot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation/tutorial: Fix markdown heading in Part 3

Browse Source 
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>
This commit is contained in:
Nicholas Chin
2022-08-23 17:51:21 -06:00
committed by Felix Held
parent 3f6de867e8
commit c39598c975
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/tutorial/part3.md
View File

@@ -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 by the code that satisfies them, the process of writing tests and adding
them to the tree is the same. them to the tree is the same.
## Analysis of unit under test First of all, it is necessary to ## Analysis of unit under test
precisely establish what we want to test in a particular module. Usually First of all, it is necessary to precisely establish what we want to
this will be an externally exposed API, which can be used by other test in a particular module. Usually this will be an externally exposed
modules. API, which can be used by other modules.
```eval_rst ```eval_rst
.. admonition:: i2c-test example .. admonition:: i2c-test example