diff --git a/docs/acknowledgment/contributors.md b/docs/acknowledgment/contributors.md
index 0e24ba0..865ff60 100644
--- a/docs/acknowledgment/contributors.md
+++ b/docs/acknowledgment/contributors.md
@@ -1,6 +1,6 @@
-We thank everyone who has contributed to making **Carch** better. Your feedback and contributions are invaluable!
+**We thank everyone who has contributed to making `Carch` better. Your feedback and contributions are invaluable!**
[](https://github.com/harilvfs/carch/graphs/contributors)
diff --git a/docs/acknowledgment/inspiration.md b/docs/acknowledgment/inspiration.md
index b8b5657..e451e5f 100644
--- a/docs/acknowledgment/inspiration.md
+++ b/docs/acknowledgment/inspiration.md
@@ -1,8 +1,20 @@
+
# Inspiration
-- **[ChrisTitusTech `linutil`](https://github.com/ChrisTitusTech)**
-- **[ML4W `Dotfiles Script`](https://github.com/mylinuxforwork)**
+- **[ChrisTitusTech `linutil`](https://github.com/ChrisTitusTech/linutil/)**
+- **[ML4W `Dotfiles Script`](https://github.com/mylinuxforwork/dotfiles)**
+
+*I have a good habit of exploring new things and trying out different ideas, whether it’s scripting or Linux-related tasks. Often, I find myself diving into scripting projects or experimenting with tools, even if it starts with just sitting around and tinkering.*
+
+One of my inspirations has been watching Chris Titus Tech's [live streams](https://www.youtube.com/@TitusTechTalk) and [videos](https://www.youtube.com/@ChrisTitusTech). Chris has been working on an amazing project called [`linutil`](https://github.com/ChrisTitusTech/linutil/). It gave me the idea to start building my own project, but in my own unique way. Initially, my project was quite basic—just a script with a `whiptail`-based TUI. It felt somewhat boring and clunky at the time.
+
+Later, I discovered another inspiring creator, ML4W (My Linux For Work), whose [Hyprland scripts and configurations](https://github.com/mylinuxforwork/dotfiles) are quite popular. After exploring their repository, I noticed he used tools like `gum` and `figlet` in their scripts. I was amazed to see how these tools added flair to bash scripting.
+
+Inspired by this, I returned to my own scripting work and implemented `gum` and `figlet` for enhanced ASCII text and user interactivity. It wasn’t an instant success—the development process took time and effort—but day by day, my script became more polished. Now, I’m quite proud of what I’ve built, and I truly enjoy using these tools in my work.
+
+**I want to thank both [Chris Titus Tech](https://github.com/ChrisTitusTech) and [ML4W](https://github.com/mylinuxforwork/) for being such incredible sources of ideas and inspiration. While I put in the work, their creativity and contributions to the Linux community have played a big role in shaping my own journey. 😊**
+
diff --git a/docs/getting-started/introduction.md b/docs/getting-started/introduction.md
index d9b6f74..d1a6212 100644
--- a/docs/getting-started/introduction.md
+++ b/docs/getting-started/introduction.md
@@ -2,40 +2,41 @@
## What is Carch?
-**Carch** is a simple yet powerful Bash script designed to simplify the process of setting up an Arch Linux system. With an intuitive menu interface powered by `gum`, Carch makes configuring your system as easy and efficient as possible, saving you valuable time.
+**Carch** is a simple `Bash script` designed to simplify the process of setting up an `Arch` Linux system. With an intuitive menu interface powered by `gum`, Carch makes configuring your system as easy and efficient as possible, saving you valuable time.
-### Features
+## Features
- **Essential Package Installation**
- Install a variety of daily-use applications, such as file managers, browsers, text editors, and more.
+ *Install a variety of daily-use applications, such as file managers, browsers, text editors, and more.*
- **Development Environment Setup**
- Easily install popular development tools like VS Code, Cursor, Vim, and Neovim, all configured for immediate use.
+ *Easily install popular development tools like VS Code, Cursor, Vim, and Neovim, all configured for immediate use.*
- **Preconfigured Configurations**
- Apply pre-setup configurations for key tools and applications, including:
- - Terminals like Kitty and Alacritty.
- - Neovim with custom themes and plugins.
+ *Apply pre-setup configurations for key tools and applications, including:*
+
+ - *Terminals like Kitty and Alacritty.*
+ - *Neovim with custom themes and plugins.*
+
- All configurations are crafted and tested to provide a seamless experience—just select and run, and your setup is ready to go!
+ **All configurations are crafted and tested to provide a seamless experience—just select and run, and your setup is ready to go!**
- **Window Manager Installation**
- Install and configure popular window managers like DWM, Hyprland, i3, and Sway, with more to come in future updates.
+ *Install and configure popular window managers like DWM, Hyprland, i3, and Sway, with more to come in future updates.*
## Why Choose Carch?
- **Time-Saving**
- Carch’s preconfigured setups let you configure your system quickly and efficiently, without the hassle of manual installation and setup.
+ *Carch’s preconfigured setups let you configure your system quickly and efficiently, without the hassle of manual installation and setup.*
- **Stable and Reliable**
- Updates are only pushed after rigorous testing to ensure stability and a bug-free experience.
+ *Updates are only pushed after rigorous testing to ensure stability and a bug-free experience.*
## GTK and CLI Support
- **GTK Version**
- A GTK-based version of Carch is available (currently in development) for a more user-friendly, graphical experience.
+ *A GTK-based version of Carch is available `(currently in development)` for a more user-friendly, graphical experience.*
- **Carch CLI**
- A command-line interface is also included for handling various instructions and tasks.
+ *A command-line interface is also included for handling various instructions and tasks.*
-With Carch, you can effortlessly handle all basic tasks and system setups. Feedback is always welcome, and we look forward to hearing from you!
+**With Carch, you can effortlessly handle all basic tasks and system setups. Feedback is always welcome, and we look forward to hearing from you!**
-Thank you for choosing Carch. 😊
diff --git a/docs/github/contributing.md b/docs/github/contributing.md
index bbc920a..e28158f 100644
--- a/docs/github/contributing.md
+++ b/docs/github/contributing.md
@@ -1,41 +1,105 @@
-# Contributing to **Carch** 🤝
+# Contributing to **Carch**
-*Contributions are welcome! If you want to help improve **Carch**, please fork the repository and submit a pull request.*
+
+
+We’re excited that you’re interested in contributing to **Carch**! Contributions of all kinds are welcome, whether you’re fixing bugs, adding new features, or improving documentation. Follow this guide to get started.
## Steps to Contribute
-1. 🍴 **Fork the repository**
- - Click the "Fork" button at the top right corner of the repository page to create your own copy of the project.
+### 1. 🍽️ Fork the Repository
+- Go to the **Carch** GitHub page.
+- Click the **Fork** button in the top-right corner to create your own copy of the repository.
+
+### 2. 🌿 Clone the Forked Repository
+- Use the following command to clone the repository to your local system:
+
+ ```bash
+ git clone https://github.com/your-username/carch.git
+ ```
+
+- Replace `your-username` with your GitHub username.
+
+:::tip :bulb: TIP
+**You can also use GUI tools like `GitHub Desktop` or even the GitHub web interface to fork and clone repositories. These tools provide an easy-to-use visual interface for managing your contributions.**
+:::
+
+### 3. 🌱 Set the Original Repository as Upstream
+- Add the original **Carch** repository as an upstream remote to keep your fork up to date:
+
+ ```bash
+ cd carch
+ ```
+
+ ```bash
+ git remote add upstream https://github.com/original-author/carch.git
+ ```
-2. 🌿 **Create a new feature branch**
- - Use a descriptive name for your branch that reflects the changes you are making.
- - For example: `feature/add-new-script`, `bugfix/fix-installation-issue`.
+### 4. 🍇 Create a New Feature Branch
+- Before making changes, create a new branch with a descriptive name:
```bash
- git checkout -b your-feature-branch-name
- ```
-3. ✏️ **Make your changes**
- - Implement your changes, ensuring that they align with the project's coding standards.
+ git checkout -b feature/your-branch-name
+ ```
+
+- Examples of branch names:
+ - `feature/add-new-script`
+ - `bugfix/fix-installation-issue`
+
+### 5. 🔧 Make Your Changes
+- Implement the necessary changes to the code or documentation.
+- Ensure that your changes are clear, tested, and follow the project’s coding standards.
+
+### 6. 📝 Stage and Commit Your Changes
+- Add the modified files to the staging area:
-4. 💬 **Commit your changes**
- - Write a clear and descriptive commit message that explains what your changes do.
-
```bash
- git commit -m "Add new feature: [brief description]"
- ````
-5. 🚀 **Push to the branch**
- - Push your changes to your forked repository.
-
-
git push origin your-feature-branch-name
+ git add .
+ ```
-6. 📥 **Submit a pull request**
- - Navigate to the original repository and click on "New Pull Request."
- - Select your feature branch and provide a description of your changes.
+- Commit your changes with a clear message:
+
+ ```bash
+ git commit -m "Add: [brief description of your changes]"
+ ```
+
+### 7. 🚀 Push the Changes to Your Fork
+- Push your branch to your forked repository:
+
+ ```bash
+ git push origin feature/your-branch-name
+ ```
+
+### 8. 📥 Submit a Pull Request (PR)
+- Go to the original **Carch** repository on GitHub.
+- Click on **New Pull Request**.
+- Select your branch from the dropdown and describe your changes in detail.
+- Submit the PR for review!
## Guidelines
-- Ensure that your code follows the existing style and conventions of the project.
-- Test your changes locally to ensure everything works as expected.
-- If your changes introduce new features, consider updating the documentation as well.
+### Code Quality
+- Follow the existing coding style of the project.
+- Write clear, concise, and well-documented code.
+
+### Testing
+- Test your changes locally to ensure they work as expected.
+- If your changes introduce new features, add necessary tests where applicable.
+
+### Documentation
+- If your changes involve new functionality, update the relevant documentation.
+- Ensure the README or Wiki reflects your updates.
+
+### Syncing Your Fork
+- Keep your fork updated to avoid conflicts:
+
+ ```bash
+ git fetch upstream
+ ```
+ ```bash
+ git merge upstream/main
+ ```
+ - Replace `main` with the default branch of the repository if it’s different.
+
+Thank you for contributing to **Carch**! Your effort helps make this project better for everyone.