From e8b6801de15dfe73dd8a311d0bdb4a1c59f708c9 Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Wed, 27 Jun 2018 12:22:08 +0200 Subject: [PATCH] Fix typo --- blog/content/second-edition/posts/05-integration-tests/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/content/second-edition/posts/05-integration-tests/index.md b/blog/content/second-edition/posts/05-integration-tests/index.md index 3856ae2f..fb84697f 100644 --- a/blog/content/second-edition/posts/05-integration-tests/index.md +++ b/blog/content/second-edition/posts/05-integration-tests/index.md @@ -26,7 +26,7 @@ Running on the target architecture allows us to test all hardware specific code [page table]: https://en.wikipedia.org/wiki/Page_table [CPU exception]: https://wiki.osdev.org/Exceptions -In this post we will implement a very basic test framework that runs integration tests inside instances of the [QEMU] virtual machine. It is not as realistic as running them on real hardware, but it is much simpler and should be suffient as long as we only use standard hardware that is well supported in QEMU. +In this post we will implement a very basic test framework that runs integration tests inside instances of the [QEMU] virtual machine. It is not as realistic as running them on real hardware, but it is much simpler and should be sufficient as long as we only use standard hardware that is well supported in QEMU. [QEMU]: https://www.qemu.org/