requirements: render markdown

bitcraze · Oct 4, 2021 · 589779c · 589779c
1 parent d778a47
commit 589779c
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 3 deletions.
diff --git a/requirements/README.md b/requirements/README.md
@@ -5,7 +5,9 @@ Requirements
 <!-- This file is auto-generated! -->
 
 
-The requirements represents what we can test about or products and devices. They are added to TOML files in this directory. The TOML files are parsed from the test framework and used as input to the tests. They are also rendered to markdown using `utils/render_requirements.py`.
+The requirements represents what we can test about or products and devices. They are added to TOML files in this 
+directory. The TOML files are parsed from the test framework and used as input to the tests. They are also rendered to 
+markdown using `utils/render_requirements.py`.
 
 Below is a list of the current groups:
 

diff --git a/requirements/decks.md b/requirements/decks.md
@@ -20,7 +20,8 @@ These requirements target the Crazyflie expansion decks.
 
 
 It must be possible to detect, by way of the parameter interface, which decks
-that are currently detected and initilized correctly on the Crazyflie.
+that are currently detected and initilized
+ correctly on the Crazyflie.
 
 |Field|Value|
 | :--- | :--- |

diff --git a/requirements/logging.md b/requirements/logging.md
@@ -23,7 +23,8 @@ These requirements targets the Crazyflie logging framework.
 
 
 It must be possible to receive logging variable values in both a synchronous and
-asynchronous manner. It must also be possible to set a desired rate of how
+asynchronous manner. It must also be 
+possible to set a desired rate of how
 often one receives updates of the logging variable.
 
 |Field|Value|