docs(README.md): add Contributors section with contrib.rocks image to acknowledge contributors

docs(permissions.md): update file paths for Sys Admin and Bot Owner from config.json to config/settings.yml for better organization
docs(permissions.md): clarify Server Owner role description for better understanding

Author: kzndotsh

Diff for: README.md

@@ -152,4 +152,12 @@ See [LICENSE](LICENSE.md) for details.
 
 ## Metrics
 
-![Alt](https://repobeats.axiom.co/api/embed/b988ba04401b7c68edf9def00f5132cd2a7f3735.svg "Repobeats analytics image")
+<sub>Made with [Repobeats](https://repobeats.axiom.co).</sub>
+
+![Metrics](https://repobeats.axiom.co/api/embed/b988ba04401b7c68edf9def00f5132cd2a7f3735.svg)
+
+## Contributors
+
+<sub>Made with [contrib.rocks](https://contrib.rocks).</sub>
+
+[![Contributors](https://contrib.rocks/image?repo=allthingslinux/tux)](https://github.com/allthingslinux/tux/graphs/contributors)

Diff for: docs/permissions.md

@@ -29,9 +29,8 @@ Below is the hierarchy of permission levels available in Tux:
 - **4: Senior Moderator**
 - **5: Administrator**
 - **6: Head Administrator**
-- **7: Server Owner**
-- **8: Sys Admin** (User ID list in `config.json`)
-- **9: Bot Owner** (User ID in `config.json`)
+- **7: Server Owner** (Not the actual discord assigned server owner)
+- **8: Sys Admin** (User ID list in `config/settings.yml`)
+- **9: Bot Owner** (User ID in `config/settings.yml`)
 
-By leveraging these permission levels, Tux provides a robust and adaptable way to manage who can execute specific commands,
-making it suitable for various server environments.
+By leveraging these permission levels, Tux provides a robust and adaptable way to manage who can execute specific commands, making it suitable for various server environments.