diff --git a/tests/unittests/README.md b/tests/unittests/README.md
index 3408f4d1619604fd38a576d5d0731d8dfc760172..df16b4acb46b7b4f1f38c1d47db12aed85e20e78 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.