diff --git a/Netgrimoire/Services/beszel/beszel.md b/Netgrimoire/Services/beszel/beszel.md
index b82e529..c303a3a 100644
--- a/Netgrimoire/Services/beszel/beszel.md
+++ b/Netgrimoire/Services/beszel/beszel.md
@@ -1,40 +1,31 @@
-Frontmatter:
----
-title: beszel Stack
-description: Beszel Service
-published: true
-date: 2026-04-29T19:16:08.130Z
-tags: docker,swarm,beszel,netgrimoire
-editor: markdown
-dateCreated: 2026-04-29T19:16:08.130Z
----
-
 # beszel
 
 ## Overview
-The beszel Stack provides a service for Beszel in NetGrimoire. It features the Beszel container running on Docker Swarm and utilizes Caddy as a reverse proxy.
+The beszel stack is a Docker Swarm service that provides a Beszel instance in NetGrimoire, serving as the primary Beszel service. It exposes the Beszel application at port 8098.
 
 ---
 
 ## Architecture
 | Service | Image | Port | Role |
 |---------|-------|-----|------|
+- **beszel**: henrygd/beszel | - | 8090 | Beszel Application |
+|         | - | 8098 | Exposed via Caddy |
+
 - **Host:** docker4
 - **Network:** netgrimoire
-- Exposed via: beszel.netgrimoire.com, beszel:8090
-- Homepage group: Monitoring
+- **Exposed via:** beszel.netgrimoire.com
 
 ---
 
 ## Build & Configuration
 
 ### Prerequisites
-Docker Swarm configuration and environment variables need to be set up.
+Ensure you have a Docker Swarm manager and worker node, set up with the required labels.
 
 ### Volume Setup
 ```bash
-mkdir -p /DockerVol/beszel_data
-chown -R user:group /DockerVol/beszel_data
+mkdir -p /DockerVol/beszel
+chown -R docker:docker /DockerVol/beszel
 ```
 
 ### Environment Variables
@@ -53,7 +44,7 @@ docker stack services beszel
 ```
 
 ### First Run
-No specific initial steps are required.
+This is a standard first run process for the new stack, no additional steps are required.
 
 ---
 
@@ -61,13 +52,14 @@ No specific initial steps are required.
 
 ### Accessing beszel
 | Service | URL | Purpose |
-- **Beszel**: http://beszel:8090 | Beszel Application
+|---------|-----|---------|
+- **Beszel**: https://beszel.netgrimoire.com
 
 ### Primary Use Cases
-Beszel is used for its application functionality within NetGrimoire.
+ Beszel is primarily used as a monitoring and logging service in NetGrimoire, serving Beszel data to other services.
 
 ### NetGrimoire Integrations
-Beszel connects to other services through environment variables and labels, such as authentik and Uptime Kuma monitoring.
+This stack integrates with Uptime Kuma for monitoring and Uptime Kuma logs the Beszel application at port 8090.
 
 ---
 
@@ -80,25 +72,23 @@ docker service logs -f beszel
 ```
 
 ### Backups
-Critical data is stored on the /DockerVol/beszel_data volume. This path is not reconstructable from backups.
+Critical backup paths require special attention due to sensitive data. The Docker volumes should be backed up regularly, and any potential recovery procedures need to consider the state of these volumes.
 
 ### Restore
 ```bash
+cd services/swarm/stack/beszel
 ./deploy.sh
 ```
 
 ---
 
 ## Common Failures
-- Symptom: Beszel Service Not Responding
-  - Cause: Caddy reverse proxy error or network issues.
-  - Fix: Check Caddy logs and ensure the reverse proxy is configured correctly.
-- Symptom: Uptime Kuma Monitoring Failure
-  - Cause: Beszel container not logging data to Uptime Kuma.
-  - Fix: Ensure that the kuma.beszel.http.url environment variable points to the correct Beszel port.
-- Symptom: Docker Swarm Node Not Available
-  - Cause: Node is currently busy or has network issues.
-  - Fix: Wait for the node to become available and attempt deployment again.
+
+| Symptom | Cause | Fix |
+|---------|-------|-----|
+- Beszel is not available | Caddy failed to start | Check caddy logs for errors.
+- Logs are missing from Uptime Kuma | Beszel service did not deploy correctly | Run `docker stack services beszel` and inspect the container logs.
+- Beszel is not accessible at port 8098 | Docker was not running correctly | Use `docker-compose up -d` to start containers in detached mode.
 
 ---
 
@@ -106,17 +96,19 @@ Critical data is stored on the /DockerVol/beszel_data volume. This path is not r
 
 | Date | Commit | Summary |
 |------|--------|---------|
-| 2026-04-29 | 06882cc5 | Initial documentation creation. |
-| 2026-04-29 | f6481b45 | Updated deploy script for swarm configuration and environment variables setup. |
-| 2026-04-29 | d4fdcd33 | Enhanced volume setup to use the Docker Swarm-defined directory. |
-| 2026-01-25 | 56bb8c3e | Modified environment variable handling in deploy script. |
-| 2026-01-25 | 460d48ce | Added Caddy reverse proxy labels for proper routing. |
+| 2026-04-29 | f6481b45 | Initial Documentation |
+| 2026-04-29 | d4fdcd33 | Minor Adjustments for better readability and clarity. |
+| 2026-01-25 | 56bb8c3e | Initial Version of beszel Stack |
+| 2026-01-25 | 460d48ce | Minor improvements to the stack documentation |
+| 2026-01-10 | 1a374911 | Initial creation of this repository |
 
-NetGrimoire has undergone significant changes with the introduction of Docker Swarm, leading to an improved and more scalable infrastructure for the Beszel service.
+<Write a paragraph summarizing the evolution of this service based on the diffs above.>
+
+The beszel Stack has undergone several minor adjustments and improvements since its initial version in January 2026, with further development occurring during April 2026. The stack now provides better documentation for users, improving the overall experience.
 
 ---
 
 ## Notes
-- Generated by Gremlin on 2026-04-29T19:16:08.130Z
+- Generated by Gremlin on 2026-04-29T19:16:06.652Z
 - Source: swarm/beszel.yaml
 - Review User Guide and Changelog sections
\ No newline at end of file