Read-only mirrors. Development, issues and pull requests are on GitHub.

summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorLeitwolf112026-11-13 17:24:13 +0300
committerLeitwolf112026-11-13 17:24:13 +0300
commita82d327e989a1d9f00d5ce9cbc60af309ba92e4c (patch)
treecb1671a57f0e39324d581456d79469db7bf8c41a
parente0d6a8c15bf123862daeb40e5cdd32e6f2f67045 (diff)
downloadprogmasoft-cpp-a82d327e989a1d9f00d5ce9cbc60af309ba92e4c.tar.gz
Speak of the guidelines in the plural and name current projects
The README follows the new plural name, and names Catch3 and Tazelish as projects that follow the guidelines; the Tala compiler is archived. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 433f344..4eafb5b 100644
--- a/README.md
+++ b/README.md
@@ -7,8 +7,8 @@ Progmasoft Core C++ Coding Guidelines are the coding guidelines of Progmasoft fo
is named, laid out, structured and checked, and why, so that a reader can move between files and projects without
relearning the conventions each time.
-It is written for anyone who wants a complete, opinionated rule set to adopt. Progmasoft's own C++ projects follow it,
-among them the [Tala compiler](https://github.com/Progmasoft/tala) and [Catch3](https://github.com/Progmasoft/catch3).
+They are written for anyone who wants a complete, opinionated rule set to adopt. Progmasoft's own C++ projects follow
+them, among them [Catch3](https://github.com/Progmasoft/catch3) and [Tazelish](https://github.com/Progmasoft/tazelish).
## How to read it