From 953281cb5e5f4f726616706556a8923f1607353a Mon Sep 17 00:00:00 2001 From: Christian Gram Kalhauge <chrg@dtu.dk> Date: Fri, 26 Nov 2021 09:53:28 +0100 Subject: [PATCH] Fix spelling mistakes --- README.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index afecc87..27f2cde 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ > eh.. It's only a model. A dynamic library for making `malloc`, `calloc`, and `realloc` return `NULL` -during tests: +during tests. Let's start with an example: ```c #include <stdio.h> @@ -61,7 +61,7 @@ Also see [test/main.c](test/main.c) and [test/main.cpp](test/main.cpp). *Why, would I ever do such a thing?* Well, most people forget to check if `malloc` returns `NULL`, or that `new` can throw an exception. By using this -library you can put a ticking time-bomb under your tests, because it better +library you can put a ticking time-bomb under your tests, because it's better to fail early than in production. ## Usage @@ -98,8 +98,8 @@ of this library. ### Valgrind -Wiht valgrind, use the `--soname-synonyms=somalloc` flag, and compile and dynamic -link using the C++ version of the library if you are testing a C++ application. +When using valgrind, use the `--soname-synonyms=somalloc` flag, and compile or dynamic +link with the C++ version of the library if you are testing a C++ application. ``` valgrind --soname-synonyms=somalloc <binary> @@ -112,5 +112,3 @@ There are courently no workaround.. yet. ### Thread Safty The library is currently not thread-safe, use with causion. - - -- GitLab