From 459d202b1bbf7abb817a596ce9374edfb7b4da8f Mon Sep 17 00:00:00 2001
From: psykose
Date: Wed, 10 Jul 2024 06:49:02 +0200
Subject: prefix special defines with FORTIFY_

just in case, and because 'PEDANTIC_CHECKS' is a really generic name
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'README.md')

diff --git a/README.md b/README.md
index 8ea8908..86e73fc 100644
--- a/README.md
+++ b/README.md
@@ -24,10 +24,10 @@ on Clang. It was initially intended to be used on
 - It has a [comprehensive suite of tests](https://github.com/jvoisin/fortify-headers/tree/master/tests),
   running both on Clang and on GCC for every commit, with
   [significant coverage](https://jvoisin.github.io/fortify-headers/)
-- Defining `USE_NATIVE_CHK` will make use of compiler-provided builtin `_chk`
+- Defining `FORTIFY_USE_NATIVE_CHK` will make use of compiler-provided builtin `_chk`
   functions, which might be a bit better in term of diagnostics,
   but won't necessarily provide the same amount of security checks.
-- Defining `PEDANTIC_CHECKS` will enable pedantic checks, that while technically
+- Defining `FORTIFY_PEDANTIC_CHECKS` will enable pedantic checks, that while technically
   correct, might break some programs relying on widely accepted
   undefined-behaviours.
 
-- 
cgit v1.3