From 07500779595c60a1899136e655071048b7bc6fb2 Mon Sep 17 00:00:00 2001 From: Pandit Dhamdhere <85685981+panditdhamdhere@users.noreply.github.com> Date: Tue, 4 Feb 2025 10:02:00 +0530 Subject: [PATCH] Update about_section_instructions.md update with minor typo. --- docs/about_section_instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/about_section_instructions.md b/docs/about_section_instructions.md index 1e71c60..307ccf8 100644 --- a/docs/about_section_instructions.md +++ b/docs/about_section_instructions.md @@ -63,7 +63,7 @@ This leads to the following practices: - lowercase > UPPERCASE #### Acronyms are bad names, usually -There is a tendancy in government to name everything that needs a name with an acronym. Acronyms save time for those that know their meaning, but they convey somewhere between very little and zero information to the people who don't know their meaning. As such, if there is a choice between using three words separated by dashes and an acronym, the three words separated by dashes is nearly always the better name. +There is a tendency in government to name everything that needs a name with an acronym. Acronyms save time for those that know their meaning, but they convey somewhere between very little and zero information to the people who don't know their meaning. As such, if there is a choice between using three words separated by dashes and an acronym, the three words separated by dashes is nearly always the better name. You can always explain in the README that internally, the project is referred to as acronym ___.