From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Mon, 26 Aug 2024 18:36:52 +0000 (-0400)
Subject: spelling: incompatibility
X-Git-Tag: rec-5.2.0-alpha1~113^2~3
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8ea621cea602cc962dd5f37831c6c7e1cdd2de2e;p=thirdparty%2Fpdns.git

spelling: incompatibility

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---

diff --git a/CODE_COVERAGE.md b/CODE_COVERAGE.md
index 778928b7bc..3eec37d953 100644
--- a/CODE_COVERAGE.md
+++ b/CODE_COVERAGE.md
@@ -20,7 +20,7 @@ This approach generates `.gcno` files during the compilation, which are stored a
 * Every invocation of a program updates the `.gcda` files corresponding to the code that has been executed. It will append to existing `.gcda` files, but only process can update a given file so parallel execution will result in corrupted data.
 * Writing to each `.gcda` might take a while for large programs, and has been known to slow down execution quite a lot.
 * Accurate reporting of lines and branches may be problematic when optimizations are enabled, so it is advised to disable optimizations to get useful analysis.
-* Note that the `.gcda` files produced by `clang++` are not fully compatible with the `g++` ones, and with the existing tools, but [`llvm-cov gcov`](https://llvm.org/docs/CommandGuide/llvm-cov.html#llvm-cov-gcov) can produce `.gcov` files that should be compatible. A symptom of this incompatiblity looks like this:
+* Note that the `.gcda` files produced by `clang++` are not fully compatible with the `g++` ones, and with the existing tools, but [`llvm-cov gcov`](https://llvm.org/docs/CommandGuide/llvm-cov.html#llvm-cov-gcov) can produce `.gcov` files that should be compatible. A symptom of this incompatibility looks like this:
 
 ```
 Processing pdns/ednssubnet.gcda