feat: update documentation with new rules, corrections, and improved clarity across multiple sections

Author: RENAH-HTTP

docs/Extracted_Rules/Extracted_Rules.md

@@ -9,28 +9,42 @@
 8. Software name capitalisation — Live (the software) and version refs like Live 12 are always capitalised.
 9. Grammar: allows/enables to — allows to and enables to are grammatically wrong. Use allows you to or lets you.
 10. Paragraph length — Max 4 sentences per paragraph. (Not enforced in Free mode)
-11. Passive voice — Avoid was added, has been updated, can be accessed. Use active voice.
+11. ~~Passive voice — Avoid was added, has been updated, can be accessed. Use active voice.~~
 12. Bug fix structure (Bug Fix mode) — Must describe both: what broke AND what now works.
 13. Release note structure (Release Note mode) — Must lead with what the user can now DO.
 14. Minimize words — Cut simply, just, easily, obviously, of course, clearly — they make tasks sound trivial.
 15. Weak sentence opener — Avoid starting sentences with There is/are or It is. Lead with the real subject.
 16. Redundant phrasing — in order to → to, due to the fact that → because, at this point in time → now, etc.
-17. Filler phrases — Cut please note, note that, it is worth noting, as you can see, etc.
+17. ~~Filler phrases — Cut please note, note that, it is worth noting, as you can see, etc.~~
+
+> **correction**: Note that is allowed
+
 18. Double spaces — Single space between words and after punctuation.
 19. Trailing ellipsis — ... at the end of a sentence implies an unfinished thought.
 20. Avoid etc. — Complete the list or write and
 21. Parameter Values - place parameter values in double quotes. 100% is "100%".
 
 **Release Note Only**
+
 1. Release note structure — must describe what the user can now DO (looks for: "can now", "lets you", "allows you", "use", "select", "access", etc.)
 
 # Bug Fix Rules
 
-1. Always lead with "Fixed" — "Fixed an issue where...", "Fixed a bug where...", "Fixed a crash that occurred when..."
+1. ~~Always lead with "Fixed" — "Fixed an issue where...", "Fixed a bug where...", "Fixed a crash that occurred when..."~~ 
+
+> **correction**: those are suggestions ...
+
 2. Platform-specific bugs — name the platform first. "Fixed an issue on macOS where...", "Fixed an issue on Windows where..."
 3. Describe the trigger — what action or condition caused the bug. Be specific.
 4. Describe the outcome — what now works. Can be a second sentence: "X now Y."
 5. Passive voice IS allowed here — "Fixed an issue where X was not Y" is the standard form. The linter skips passive checks in Bug Fix mode.
 6. Use bullet points for multiple related fixes in the same release.
-7. No crash without a trigger — "Fixed a crash" alone is not enough. State what caused it.
-8. All standard rules still apply — American English, UI element caps, no marketing, no dev jargon, no contractions, acronym caps, etc.
+7. ~~No crash without a trigger — "Fixed a crash" alone is not enough. State what caused it.~~
+
+> **correction**: those are suggestions ...
+
+8. All standard rules still apply — American English, UI element caps, no marketing, no dev jargon, no contractions, acronym caps, etc. 
+
+9. Max 2 sentences.. or as short as possible.
+
+10. Improvements, features and more - start with the main subject instead of "Fixed"

docs/Extracted_Rules/Update_Log.md

@@ -1,4 +1,7 @@
 # Update Log
 
-- 11 May — added rule nr. 21 "Parameter Values"
+- 17 May - Added Bug Fix rules 9. and 10.
+- 16 May - Added corrections on Bug Fix rules 1., 7. and on General rule 1.
+- 15 May - Flagged 11. Passive voice and crosses it out. 
+- 11 May — Added rule nr. 21 "Parameter Values"
 - 09 May — Created the Rules list

docs/Git/Git_Learning_Notes.md

@@ -1,12 +1,12 @@
 # Git Notes
 
-Stuff I actually did and understand. Short form.
+Stuff I actually did and understand :)
 
 ---
 
 ## Mental model
 
-- branch = full snapshot of repo, not a folder
+- branch = full snapshot of repo, not a folder...
 - commit = photo of every file at one moment, has a hash
 - branch label = sticky note pointing at one commit
 - `HEAD` = "you are here"
@@ -40,7 +40,7 @@ git add Writing_Rules/Writing_Rules.md   # stage
 git commit -m "feat: add more writing rules"   # commit
 ```
 
-forgot to stage once → got "nothing to commit, working tree clean"
+I forgot to stage once and got "nothing to commit, working tree clean"
 `git status` shows it. red = unstaged, green = staged.
 
 ### unstaging
@@ -51,7 +51,7 @@ git restore --staged <file>   # undo a git add
 ### undoing commits
 ```
 git reset --soft HEAD~1    # undo last commit, keep changes staged
-git reset --hard HEAD~1    # undo last commit + delete changes ⚠️
+git reset --hard HEAD~1    # undo last commit + delete changes 
 ```
 
 `HEAD~1` = one commit back
@@ -69,8 +69,13 @@ git merge writing-rules     # pull writing-rules into main
 git push
 ```
 
-merge opened Vim asking for a message. exit Vim: `Esc`, then `:wq`, Enter.
-my merge used the 'ort' strategy = true merge with a merge commit (not fast-forward).
+merge opened Vim asking for a message. Vim = a text editor inside the terminal. no mouse, only keys.
+exit Vim: `Esc`, then type `:wq`, Enter. (`:wq` = save and quit)
+
+my merge said it used the 'ort' strategy. from what I get so far:
+- if nothing new is on `main`, git just glues the new commits on the end → no message needed
+- if both branches have new stuff, git makes one extra commit to join them → that's what needed a message
+- 'ort' is just the name of the recipe git uses to combine them. don't really get the details yet, still looking into it.
 
 ### deleting a branch (local only)
 ```

docs/Journal/16_May.md

@@ -2,12 +2,19 @@
 
 ## Situation
 
+End of the week and I'm barely using AI anymore. It keeps getting the rules wrong, and I spend most of the time denying its suggestions instead of accepting them.
 
 ## Task
 
+Trust you instinct an stop using help. 
 
 ## Action
 
+AI — started the week using it as a learning tool, which worked. But by now its facts about the rules are off enough that I'm correcting more than I'm getting. Pulled back on checking with it.
 
 ## Result
 
+- My writing is consistenly right the first time.
+
+---
+

docs/Journal/17_May.md

@@ -1,13 +1,28 @@
 # Sunday, 17 May
 
 ## Situation
-
+Numbers written as digits in places they shouldn't be. Bug entries and improvement entries blending into each other. Also wanted to spend time on git outside of just using it for commits.
 
 ## Task
-
+Pin down new small rules — number style, bug entry shape, improvement entry shape. Practice git and start a dedicated git page in the docs.
 
 ## Action
+Numbers — should be spelled out. "three" not "3". At least for low numbers in prose.
+
+Bug entries — always start with "Fixed". Two shapes I keep seeing:
+- `Fixed [device] [problem]` — e.g. "Fixed Drum Sampler crash on load."
+- `Fixed [adjective] [noun]` — e.g. "Fixed incorrect parameter naming."
 
+Improvements / features — lead with the improved thing, not the action. The feature is the subject.
+
+Git — practiced branching, merging, and pushing on the side. Made a Git page in the docs to write down what I actually understand.
 
 ## Result
+Three small rules locked in:
+
+1. Numbers spelled out ("three", not "3").
+2. Added a new rule in the Bug Fix section (rule 9 and 10)
+3. New Git page in the docs — notes from actual use, not copy-pasted commands.
+
+---
 

docs/Manual/00_manual.md

@@ -1,4 +1,5 @@
 # Live 12 Manual
 
-This site is an **example and mockup** of the manual I would write for Ableton Live.
+Here you can preview an **example and mockup** of the manual entries I would write for Ableton Live.
+
 It’s intended for interview purposes: to demonstrate structure, tone, and how I would explain workflows, fixes and improvements.

docs/Questions & Notes/Notes.md

@@ -1,7 +1,11 @@
 # Notes
 
-1. Duplicate!
+1. Duplicate Found!
 
 ```
 Fixed an issue where it was not possible to navigate back to the Splice label with the Browse Back and Browse Forward buttons after navigating to other labels in the browser. This change also makes it possible to use these buttons to navigate to the Cloud label even when Cloud is not authorized, as well as to the Max for Live label even when Max is not available.
 ```
+
+2. Bug Found in Live 12.4 Suite
+
+Using the Control / Command + J keyboard shortcut for joining clips while the Audio Engine was off is not working.

docs/Questions & Notes/Questions.md

@@ -1,6 +1,8 @@
 # Questions
 
-### 1. In this example - the **return track** is not capitalized:
+### Question 1
+
+ In this example - the **return track** is not capitalized:
 
 ```
 The original signal (which was received at Beat Repeat’s input) is mixed with Beat Repeat’s repetitions according to one of three mix modes: Mix allows the original signal to pass through the device and have repetitions added to it; Insert mutes the original signal when repetitions are playing but passes it otherwise; and Gate passes only the repetitions, never passing the original signal. Gate mode is especially useful when the effect is housed in a return track.
@@ -11,7 +13,9 @@ The original signal (which was received at Beat Repeat’s input) is mixed with
 
 ---
 
-### 2. Does Wander continuously generate a new random signal (smooth, unsynced, always moving), or does it produce a new random shape once per LFO cycle?
+### Question 2
+
+Does Wander continuously generate a new random signal (smooth, unsynced, always moving), or does it produce a new random shape once per LFO cycle?
 
 ```
 Select one of the following LFO waveforms via the Wave drop-down: Sine, Triangle, Ramp Up, Ramp Down, Square, S&H (Sample and Hold), or Wander. You can further shape the selected waveform using the Morph slider.
@@ -22,7 +26,9 @@ Select one of the following LFO waveforms via the Wave drop-down: Sine, Triangle
 
 ---
 
-### 3. What does Morph specifically transform for each wave shape? For example — does it change pulse width on Square, skew the peak on Sine, bend the slope on Triangle?
+### Question 3
+
+What does Morph specifically transform for each wave shape? For example — does it change pulse width on Square, skew the peak on Sine, bend the slope on Triangle?
 
 ```
 Select one of the following LFO waveforms via the Wave drop-down: Sine, Triangle, Ramp Up, Ramp Down, Square, S&H (Sample and Hold), or Wander. You can further shape the selected waveform using the Morph slider.
@@ -33,23 +39,9 @@ Select one of the following LFO waveforms via the Wave drop-down: Sine, Triangle
 
 ---
 
-### 4. Is future passive voice permitted?
-
-```
-You will then be prompted to select a tag group or parent tag for the newly created tag. Type the name of an existing tag group or parent tag, or type your desired name and select either the Create new parent tag… or Create new tag group… option.
-```
-
-Also here:
-
-```
-Note that this mode is not yet implemented in Live, but is expected to be implemented in a future update.
-```
-
-- [Release Notes Live 12.4](https://www.ableton.com/en/release-notes/live-12/)
-
----
+### Question 4
 
-4. How can we decide what tense we use?
+How can we decide what tense we use?
 
 ```
 The filter decay in Drum Sampler's 8bit effect can now be disabled by turning the decay parameter all the way up.

docs/Release_Note/00_release_notes.md

@@ -4,15 +4,15 @@
 
 ## About This Document
 
-This document includes mockup release notes for Ableton Live 12.4. 
+This document includes mockup release notes for Ableton Live 12.4 and 12.3
 
 ## How to Use This Document
 
-- Use the navigation on the left to jump to a specific version.
+- You can use the navigation on the left to switch to a specific version.
 - Each version section lists new features, improvements, and bug fixes.
-- Screenshots and diagrams are included where relevant to help illustrate changes.
 
 ## Versions Covered
 
-Live 12.4 
-Live 12.3 - partially
+- Live 12.4 
+
+- Live 12.3 (partially)

docs/index.md

@@ -3,6 +3,22 @@
 
 Hello, my name is Theodor, and I created this website as a way to present my progress for the interview for the Technical Writing position at Ableton. 
 
-Has multiple sections which a journal, questions, a exercises I have done, release notes and everything I could think of. You can navigate through this website using the sections present on the top of your screen or on the top left - marked by three horizontal lines - depending on your window size. 
+It has multiple sections:
+
+- Manual
+
+- Release Notes
+
+- Old Versions / First Practice 
+
+- Git & Github
+
+- Journal
+
+- Extracted Rule
+
+- Questions & Notes
+
+You can navigate through this website using the sections present on the top of your screen or on the top left - marked by three horizontal lines - depending on your window size. 
 
 Thank you :)