diff --git a/next/guidelines.html b/next/guidelines.html
index a070e98f4..05369a497 100644
--- a/next/guidelines.html
+++ b/next/guidelines.html
@@ -424,7 +424,7 @@ writing by <a href="../contact.html">contacting the judges</a>.</p>
 <h2 id="ioccc-guidelines-version">IOCCC Guidelines version</h2>
 </div>
 <p class="leftbar">
-These <a href="guidelines.html">IOCCC guidelines</a> are version <strong>28.13 2024-08-22</strong>.
+These <a href="guidelines.html">IOCCC guidelines</a> are version <strong>28.14 2024-08-24</strong>.
 </p>
 <p><strong>IMPORTANT</strong>: Be <strong>SURE</strong> to read the <a href="rules.html">IOCCC rules</a>.</p>
 <div id="change_marks">
@@ -905,11 +905,25 @@ compiler produces a different result: so your submission won’t be penalized fo
 not meeting your claims).
 </p>
 <p class="leftbar">
+On the other hand, some warnings cannot be disabled and are enabled by compilers
+without any warning option specified. These are sometimes inevitable in
+obfuscated code and even in some non-obfuscated code.
+</p>
+<p class="leftbar">
+Additionally, some compilers like to warn about certain use of <code>char *</code>s which
+is not only likely dubious itself it obviously can’t (always) be avoided so you should
+not worry about this either; this is the warning <code>-Wno-unsafe-buffer-usage</code>. See
+also the
+FAQ on “<a href="../faq.html#forced_warnings">forced warnings</a>”
+and the
+FAQ on “<a href="../faq.html#weverything"><code>-Weverything</code></a>”.
+</p>
+<p class="leftbar">
 If your submission issues lots of warnings but is otherwise
 marvelously obfuscated in multiple levels, don’t worry about it. Nevertheless,
 be sure that the warnings do not constitute a potential “<strong>show stopper</strong>”
 compiler problem. Be sure that compilers such as both <code>gcc</code> and <code>clang</code> won’t
-produce a compile <strong>error</strong> and refuse to compile your code: unless for some
+produce a compiler <strong>error</strong> and refuse to compile your code: unless for some
 reason that is what you intend to happen in which case document that too in your
 <code>remarks.md</code> file. :-)
 </p>
diff --git a/next/guidelines.md b/next/guidelines.md
index 85b29f7f2..b7ebc1736 100644
--- a/next/guidelines.md
+++ b/next/guidelines.md
@@ -48,7 +48,7 @@ writing by [contacting the judges](../contact.html).
 </div>
 
 <p class="leftbar">
-These [IOCCC guidelines](guidelines.html) are version **28.13 2024-08-22**.
+These [IOCCC guidelines](guidelines.html) are version **28.14 2024-08-24**.
 </p>
 
 **IMPORTANT**: Be **SURE** to read the [IOCCC rules](rules.html).
@@ -651,12 +651,28 @@ compiler produces a different result: so your submission won't be penalized for
 not meeting your claims).
 </p>
 
+<p class="leftbar">
+On the other hand, some warnings cannot be disabled and are enabled by compilers
+without any warning option specified. These are sometimes inevitable in
+obfuscated code and even in some non-obfuscated code.
+</p>
+
+<p class="leftbar">
+Additionally, some compilers like to warn about certain use of `char *`s which
+is not only likely dubious itself it obviously can't (always) be avoided so you should
+not worry about this either; this is the warning `-Wno-unsafe-buffer-usage`. See
+also the
+FAQ on "[forced warnings](../faq.html#forced_warnings)"
+and the
+FAQ on "[`-Weverything`](../faq.html#weverything)".
+</p>
+
 <p class="leftbar">
 If your submission issues lots of warnings but is otherwise
 marvelously obfuscated in multiple levels, don't worry about it.  Nevertheless,
 be sure that the warnings do not constitute a potential "**show stopper**"
 compiler problem.  Be sure that compilers such as both `gcc` and `clang` won't
-produce a compile **error** and refuse to compile your code: unless for some
+produce a compiler **error** and refuse to compile your code: unless for some
 reason that is what you intend to happen in which case document that too in your
 `remarks.md` file.  :-)
 </p>