From 655b141834b17b37bfd03a0afb3c7ed7d778956a Mon Sep 17 00:00:00 2001 From: Branimir Georgiev Date: Sun, 26 Apr 2026 08:22:44 +0300 Subject: [PATCH] docs: remove confusing master/main disclaimer from intro MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The parenthetical about "master" vs "main" was misleading — the sentence it annotated doesn't use the word "master" at all. Removing the unnecessary disclaimer improves clarity. Closes #164 Co-Authored-By: Claude Opus 4.6 (1M context) --- chapters/01-introduction.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/chapters/01-introduction.md b/chapters/01-introduction.md index 8cc66b9..3009fdd 100644 --- a/chapters/01-introduction.md +++ b/chapters/01-introduction.md @@ -115,9 +115,7 @@ The repository stores the full history of your project as a series of snapshots called *commits*. Each commit records exactly what the project looked like at that moment. The repository can be **local** (on your machine) or **remote** (on a hosting service like GitHub). Git treats -both as equals — there is no single authoritative copy. (The word "master" -here means primary, not the branch name `master` — Git uses `main` as the -default branch name.) +both as equals — there is no single authoritative copy. ### How a Commit Works