From 48b4b542d4e48c40eb9f78b3abe05749beca5bf1 Mon Sep 17 00:00:00 2001 From: Anthony Howe Date: Thu, 27 Nov 2025 07:40:38 -0500 Subject: [PATCH] Minor spell and grammar changes. Fix Markdown anchor-name section restoring `
` and some formatting. --- markdown.md | 37 ++++++++++++++++++------------------- next/rules.md | 12 ++++++------ 2 files changed, 24 insertions(+), 25 deletions(-) diff --git a/markdown.md b/markdown.md index 170f4a33a..84a5de1a3 100644 --- a/markdown.md +++ b/markdown.md @@ -50,9 +50,12 @@ not apply to other markdown files), **PLEASE** start at level three up to level ``` ❌ ... -✔️ ... +✔️
...
+✔️ +✔️ ### Section title ``` + ## Markdown links instead of `...` @@ -105,7 +108,7 @@ We request that you indent the code block by multiples of four (4) ASCII SPACES, never TAB (␉): ```` -✔️ echo "This code block is indented by multiples of 4 spaces" +✔️ echo "This code block is indented by multiples of 4 spaces" ✔️ # The top level starts with a 4 ASCII space indent. ✔️ # @@ -143,7 +146,7 @@ ASCII SPACES. ❌ ␉Please do **NOT**␉use ASCII tabs␉in markdown files. ❌ ␉␉Please do **NOT** indent markdown with ASCII tabs. -❌ ␉We don't␉mind␉tabs␉in␉general, +❌ ␉We␉don't␉mind␉tabs␉in␉general, ❌ ␉We just ask that you NOT use them in markdown files. ``` ```` @@ -152,16 +155,16 @@ And to clarify, we are only talking about markdown files, not C code or any other non-markdown content: ```` -✔️ printf("It is fine␉to␉use tabs in Obfuscated C code.\n"); -✔️ /*␉if␉you␉wish */ +✔️ ␉printf("It is fine␉to␉use tabs in Obfuscated C code.\n"); +✔️ ␉␉/*␉if␉you␉wish */ -✔️ // We ask that you to NOT use ASCII tab characters in your remarks.md writeup, -✔️ // or in any other markdown files within your entry, please. +✔️ ␉// We ask that you to NOT use ASCII tab characters in your remarks.md writeup, +✔️ ␉// or in any other markdown files within your entry, please. ```` -**NOTE**: Again, you are **perfectly welcome** to use ASCII tab characters -in your C code and other non-markdown files. We simply ask that -you do **NOT** use any ASCII TAB (␉) characters in markdown files. +**NOTE**: Again, you are **perfectly welcome** to use ASCII TAB (␉) characters +in your C code and other non-markdown files. We simply ask that you do +**NOT** use any ASCII TAB (␉) characters in markdown files.
@@ -225,10 +228,8 @@ block as this makes it easier to detect when markdown code blocks are ## Do not add trailing slash to void HTML tags. -Please do **NOT** use a trailing slash on -[void HTML elements](https://github.com/validator/validator/wiki/Markup-»-Void-elements). - -See also this note on [trailing slashes in void-element start tags](https://github.com/validator/validator/wiki/Markup-»-Void-elements#trailing-slashes-in-void-element-start-tags-do-NOT-mark-the-start-tags-as-self-closing). +Please do **NOT** use a trailing slash on [void HTML elements](https://github.com/validator/validator/wiki/Markup-»-Void-elements). See also +this note on [trailing slashes in void-element start tags](https://github.com/validator/validator/wiki/Markup-»-Void-elements#trailing-slashes-in-void-element-start-tags-do-NOT-mark-the-start-tags-as-self-closing). The trailing slash on void HTML elements has no effect and interacts badly with unquoted attribute values. @@ -275,7 +276,7 @@ a markdown line with a trailing backslash (`\`). Instead use a trailing ```` Doing it this way will prevent `pandoc(1)` from generating deprecated -HTML elements such as `
`. +HTML elements, such as `
`.
@@ -312,8 +313,6 @@ Such markdown causes `pandoc(1)` to generate `
`. The `
` has no effect in standard HTML 5 and interacts badly with unquoted attribute values. -If a horizontal line is really needed, use: - ``` ❌ * * * ❌ - - - @@ -370,6 +369,6 @@ go for when it is **_bold and italic_**. ✔️ **_this text is bold italic_** ✔️ _**this text is bold italic**_ ``` -**BTW**: the astute reader might notice that some cases of `*` for -italic might have slipped through. We do ask you, however, to please +**BTW**: the astute reader might notice that some cases of `*` for italic +might have slipped through. We do ask you, however, to please observe this rule, as best you can. diff --git a/next/rules.md b/next/rules.md index d6427c99e..df55cda95 100644 --- a/next/rules.md +++ b/next/rules.md @@ -32,7 +32,7 @@ app from time to time to view IOCCC mastodon updates. Copyright © 2025 Leonid A. Broukhis and Landon Curt Noll. All Rights Reserved. Permission for personal, education or non-profit use is -granted provided this this copyright and notice are included in its entirety +granted provided this copyright and notice are included in its entirety and remains unaltered. All other uses **MUST** receive prior permission in writing by [contacting the judges](../contact.html). @@ -267,8 +267,8 @@ and
Entries requiring human interaction to be initially compiled are **NOT** -permitted. However, see the guidelines. Each entry **MUST** automated the -its build process using `bash`, `gmake`, `gcc`, `clang`, under a +permitted. However, see the guidelines. Each entry **MUST** automate the +build process using `bash`, `gmake`, `gcc`, `clang`, under a [SUS environment](https://pubs.opengroup.org/onlinepubs/9799919799/). Note references to `gmake` can be any GNU Make compatible tool. @@ -277,7 +277,7 @@ See [Rule 15 - Building](rules.html#rule-15---building).
-Rule 10 - Privileges +## Rule 10 - Privileges
Programs that require special privileges (setuid(2), setgid(2), @@ -368,7 +368,7 @@ didn't previously win, then you are encouraged to mention this in your The `Makefile` **MUST** adhere to GNU Makefile syntax. Its recommended -that you copy and rename the `Makefile.example` as template. The primary +that you copy and rename the `Makefile.example` as a template. The primary target of the `Makefile` **MUST** be `prog` and the source file is `prog.c`. The C compiler and preprocessor **MUST** be invoked using `${CC}` and `${CPP}` macros respectively. @@ -491,5 +491,5 @@ See also the [FAQ](../faq.html). Consider joining the [IOCCC Discord Server](https://discord.com/invite/Wa42Qujwnw) for discussions about The Rules, questions for the Judges, and `C` in general. -Leonid A. Broukhis +Leonid A. Broukhis chongo (Landon Curt Noll) /\\cc/\\