Fix typos and improve clarity in documentation; update placeholder content in output files

Author: roktiw

.DS_Store

@@ -6,7 +6,7 @@ for publishing things that matter — without starting a startup.
 *Minimum code, maximum outcomes.*
 *WHAM! BAM! And you have a static page man!*
 
-GAMstack is the natural and inevitable spritual successor to legacy software stacks such as:
+GAMstack is the natural and inevitable spiritual successor to legacy software stacks such as:
 
 - **JAMstack** (JavaScript, APIs, and Markup) – because JavaScript is bloated and Markdown was doing just fine.
 - **MACH** (Microservices, API-first, Cloud-native, and Headless) – because microservices are just meetings in disguise.
@@ -79,14 +79,13 @@ Ideal for:
 
 ## 🔄 How It Works
 
-1. **Content Management**:
-   - Store content in `posts/` as Markdown files (`.md`)
-   - Each file = one post
+1. **Content Management System**:
+   - Store content in `input/` as Markdown files (`.md`)
+   - Each file = one post 
 
 2. **GitHub Actions**:
-   - Workflow watches for changes in `posts/`
-   - Runs `update-index.js` to regenerate `index.html`
-   - Converts `.md` to `.html` and stores in `output/`
+   - Workflow blindly converts all `.md` items in folder `input/` to `.html` and outputs into `output/`
+   - GitHub Action regenerates `index.html` with a list of `.html` files
 
 3. **GitHub Pages**:
    - Hosts everything statically
@@ -95,39 +94,46 @@ Ideal for:
 
 ---
 
-## ✍️ Getting Started
+## ✍️ Start your blog, website, or another compulsive ADHD adventure
 
-1. **Clone the repo**:
-   ```bash
-   git clone https://github.com/your-repo/gam-stack.git
-   cd gam-stack
-   ```
+1. **Clone this repo**:
 
-2. **Add a new post**:
-   ```markdown
-   # My New Post
-
-   Markdown is cool.
-   ```
+2. **Add a `.md` file to `/input/` folder**:
 
 3. **Commit & Push**:
-   ```bash
-   git add .
-   git commit -m "Add new post"
-   git push
-   ```
 
-4. **Profit**:
+4. **HTML page will appear in `/output/` and `index.html` will be regenerated with a list of all pages**
+
+5. **Profit**:
    - Open your GitHub Pages URL
    - Bask in the glow of functional minimalism
 
 ---
 
+## 🌐 Setting Up GitHub Pages
+
+1. **Enable your GitHub Pages**:
+   - Clone GAMstack repository https://github.com/roktiw/gamstack
+   - Go to your cloned GAMstack repository on GitHub portal.
+   - Go to repository `Settings`
+   - Rename your `Repository name` to `YOUR_GITHUB_USERNAME.github.io`
+   - Click "Rename" button.
+
+   If sth not works, check out official GitHub Pages documentation https://docs.github.com/en/pages/quickstart
+
+2. **Verify Deployment**:
+   - After a few moments, your site will be live at `https://OUR_GITHUB_USERNAME.github.io/`.
+
+3. **Write a new note every day**
+   - Writing helps your brain to rewire and makes you live longer 
+
+---
+
 ## 🙌 Contributing
 
 PRs welcome. But only if they make things simpler.
 
 ---
 
-© Wiktor Świtkowski 2025 – [GAMstack™](https://github.com/wiktor-switkowski)  
-Built with love, Markdown and passive aggression toward bloated tooling.
+© Wiktor Świątkowski 2025 – [GAMstack™](https://github.com/wiktor-switkowski)  
+Built with love, in Warsaw, using Markdown and passive aggression toward bloated tooling.

README.md

@@ -1,13 +1,15 @@
 # How to input for GAMstack
 
-Just write a Markdown note.
+Just write a Markdown note. Seriously, that's it. No YAML, no JSON, no "microservice orchestration pipeline." Just Markdown. It's like writing a love letter to simplicity.
 
-You can use vscode, or directly create file on GitHub. Anything goes as long as the .md file goes into this beautiful `/input/` folder.
+You can use VS Code, or directly create a file on GitHub. Heck, you could even use Notepad if you're feeling nostalgic. Anything goes as long as the `.md` file lands in this sacred `/input/` folder.
 
-Yes. Its that simple.
+Yes. It's that simple. No, really. Stop overthinking it.
 
-## How I will know that magic works?
+## How will I know that the magic works?
 
-You will see this file in `/output/` folder
+You will see this file in the `/output/` folder. Yes, you. Reading this file. Twice. First as a humble `.md` file, and then as a glorious `.html` file. It's like watching your code grow up and graduate.
 
-## See you on the HTML side!
+## See you on the HTML side!
+
+(And don't forget to wave at your Markdown file on the way out. It worked hard to get here.)

input/how-to-input.md

@@ -1,3 +1 @@
-# Yes
-
-It is that simple!
+this markdown file is just a placeholder, like a movie extra waiting for its big break. Feel free to kick it out when the real star arrives!