diff --git a/processing-steps.md b/processing-steps.md
deleted file mode 100644
index 3ceae2f..0000000
--- a/processing-steps.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# Processing Steps for Creating Ansible Playbook
-
-This document details the steps followed to create and manage the Ansible playbook for applying system updates.
-
-1. **Analyze Home Directory for Existing Git Repositories**
-   - Used `find /home/grok -type d -name ".git"` to list existing repositories.
-   - Found: file-sorting-process, utility-scripts, ansible-inventories, cheatsheets.
-
-2. **Create a New Git Repository**
-   - Decided on a new repository named 'ansible-playbooks' as no existing one was suitable for Ansible playbooks.
-   - Created the repository on Gitea using API: `curl -u <creds> -X POST http://10.10.10.254:3000/api/v1/user/repos -d '{"name": "ansible-playbooks"}'`.
-   - Locally: `mkdir ansible-playbooks`, `git -C ... init`, added remote `ssh://git@127.0.0.1:2222/grok/ansible-playbooks.git`.
-
-3. **Check and Install Tools**
-   - Verified `yamllint`, `ansible-lint`, and `ansible` are installed using `which`.
-   - All were already present; no installations needed.
-
-4. **Create the Playbook File**
-   - Created `/home/grok/ansible-playbooks/update-system.yml` with content for updating Debian and RedHat-based systems.
-   - Used `create_file` tool.
-
-5. **Validate and Lint the Playbook**
-   - Ran `yamllint` and fixed 'yes' to 'true' using `str_replace_editor`.
-   - Ran `ansible-lint` and fixed by adding FQCN (e.g., ansible.builtin.apt) and '# noqa package-latest' for relevant tasks.
-
-6. **Commit and Push to Gitea**
-   - Renamed branch to 'main': `git branch -m master main`.
-   - Added file: `git add update-system.yml`.
-   - Committed: `git commit -m "Add update-system Ansible playbook for applying system updates"`.
-   - Pushed: `git push origin main` (after fixing remote URL for SSH port).
-
-7. **Create This Steps File**
-   - Created this `processing-steps.md` to document the process.
-
-8. **Commit and Push Steps File**
-   - Will commit and push this file to the repository.
diff --git a/update-system.yml b/update-linux-system.yml
similarity index 100%
rename from update-system.yml
rename to update-linux-system.yml
diff --git a/windows-updates/windows-system-updates.yml b/update-windows-system.yml
similarity index 100%
rename from windows-updates/windows-system-updates.yml
rename to update-windows-system.yml
diff --git a/windows-updates/steps.md b/windows-updates/steps.md
deleted file mode 100644
index e7874d7..0000000
--- a/windows-updates/steps.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# Steps Followed to Create the Ansible Playbook
-
-Below is a detailed explanation of the steps taken to process the user's request to create an Ansible playbook for applying system updates to various Windows systems, following the custom instructions.
-
-1. **Created a TODO List**: Planned the tasks using create_todo_list to break down the process into manageable steps.
-
-2. **Analyzed Home Directory for Existing Git Repositories**: Used bash command `find /home/grok -type d -name ".git"` to identify existing repositories. Found several, including 'ansible-playbooks'.
-
-3. **Decided on Repository**: Chose the existing 'ansible-playbooks' repository as it was suitable for Ansible-related code. Planned to create a subdirectory 'windows-updates' for organization.
-
-4. **Researched and Designed the Playbook**: Drew from knowledge of Ansible's win_updates module (from Ansible documentation and web resources like docs.ansible.com). Designed a simple playbook to install security, critical, and rollup updates with reboot handling.
-
-5. **Created Subdirectory**: Used bash `mkdir /home/grok/ansible-playbooks/windows-updates` to create the subdirectory.
-
-6. **Created the Playbook File**: Used create_file to write 'windows-system-updates.yml'. Encountered an issue with literal \n in content, leading to invalid YAML. Deleted the file and recreated it with actual newlines in the content parameter.
-
-7. **Validated the Playbook**: Ran `ansible-playbook --syntax-check` to check syntax, which passed with warnings about inventory (expected).
-
-8. **Linted the Playbook**: Ran `ansible-lint` which reported a yaml[truthy] violation. Fixed by replacing 'reboot: yes' with 'reboot: true' using str_replace_editor. Re-ran lint, which passed.
-
-9. **Committed and Pushed Changes**: Used git commands with -C option (e.g., `git -C /home/grok/ansible-playbooks add windows-updates`, commit, push) to add the new files to the repository and push to Gitea.
-
-10. **Created This Explanation File**: Created 'steps.md' to document the process, as per instructions.
-
-This ensures all actions are tracked, code is versioned in Gitea, and follows best practices for security and efficiency.