From fef429e16bf3e64a77ca47940a661cc5570fe2d6 Mon Sep 17 00:00:00 2001
From: Lotte Steenbrink <lotte@zombietetris.de>
Date: Wed, 20 Jul 2016 12:20:50 +0200
Subject: [PATCH] fix typo

---
 tests/unittests/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/unittests/README.md b/tests/unittests/README.md
index 3408f4d161..df16b4acb4 100644
--- a/tests/unittests/README.md
+++ b/tests/unittests/README.md
@@ -92,7 +92,7 @@ make term
 ## Writing unit tests
 ### File struture
 RIOT uses [*embUnit*](http://embunit.sourceforge.net/) for unit testing.
-All unit tests are organized in ``tests/unittests`` and can be build module-wise, if needed.
+All unit tests are organized in ``tests/unittests`` and can be built module-wise, if needed.
 For each module there exists a ``tests-<modulename>/tests-<modulename>.h`` file, at least one C file in ``tests-<modulename>/`` and a ``tests-<modulename>/Makefile``.
 It is recommended to add a C file named ``tests-<modulename>/tests-<modulename>-<headername>.c`` for every header file that defines functions (or macros) implemented in the module.
 If there is only one such header file ``tests-<modulename>/tests-<modulename>.c`` should suffice.