summary refs log tree commit diff
diff options
context:
space:
mode:
authorMunyoki Kilyungi2024-09-25 16:04:07 +0300
committerBonfaceKilz2024-09-30 11:22:26 +0300
commite88a3c14ba42cbf9eb974fb75014648d4f131de0 (patch)
tree44e28b1a7ada9921c97f3095778aa3f73a861405
parent60b1ae529301021c206369024462541d9df1415c (diff)
downloadgn-gemtext-e88a3c14ba42cbf9eb974fb75014648d4f131de0.tar.gz
Fix typo.
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
-rw-r--r--topics/engineering/using-architecture-decision-records-in-genenetwork.gmi2
1 files changed, 1 insertions, 1 deletions
diff --git a/topics/engineering/using-architecture-decision-records-in-genenetwork.gmi b/topics/engineering/using-architecture-decision-records-in-genenetwork.gmi
index c88398b..34a9777 100644
--- a/topics/engineering/using-architecture-decision-records-in-genenetwork.gmi
+++ b/topics/engineering/using-architecture-decision-records-in-genenetwork.gmi
@@ -3,7 +3,7 @@
 * author: bonfacem
 * reviewed-by: fredm
 
-> One of the hardest things to track during the life of a project is the motivation behind certain decisions.  A new person coming on to a project my be perplexed, baffled, delighted, or infuriated by some past decision.
+> One of the hardest things to track during the life of a project is the motivation behind certain decisions.  A new person coming on to a project may be perplexed, baffled, delighted, or infuriated by some past decision.
 > -- Michael Nygard
 
 When building or maintaining software, there's often moments when we ask, "What were they thinking?"  This happens when we are trying to figure out why something was done a certain way, leading to speculation, humor, or criticism[0].  Given the constraints we face when writing code, it's important to make sure that important decisions are well-documented and transparent.  Architecture Decision Records (ADRs) are one such tool.  They provide a structured way to capture the reasoning behind key decisions.