Commit daily changes

Signed-off-by: TrueCharts-Bot <bot@truecharts.org>

charts/stable/external-dns/docs/setup-guide.md

@@ -30,10 +30,10 @@ When using API Token authentication, the token should be granted Zone Read, DNS
 
 - Enter preferences for Logs and DNS updates (Suggested >5m to prevent log spam)
 - Set `cloudflare` as provider
-- set sources `ingress` and `service` should covers everything. 
+- set sources `ingress` and `service` should covers everything.
 - If you want to filter by multiple domains add your `domainFilters`
-- Recommend using `noop` for `registry` and leaving the rest as default, 
+- Recommend using `noop` for `registry` and leaving the rest as default,
-- You can add DNS Zone filters `zoneidFilters` as necessary as well 
+- You can add DNS Zone filters `zoneidFilters` as necessary as well
 
 For more details of all option, see upstream docs of external-dns.
 
@@ -46,7 +46,7 @@ externaldns:
   sources:
     - "service"
     - "ingress"
-  domainFilters: 
+  domainFilters:
     - "${BASE_DOMAIN}"
   zoneidFilters: []
   cloudflareProxied: ""

charts/stable/homepage/docs/hp-integration.md

@@ -4,7 +4,7 @@ title: Homepage TrueCharts Integration Guide
 
 TrueCharts has adopted `Homepage` as its default dashboard application due to its support for Kubernetes.
 
-This guide will cover how to use the TrueCharts/Homepage integration included in the charts. 
+This guide will cover how to use the TrueCharts/Homepage integration included in the charts.
 Editing the configuration .yaml files of homepage can be done if you add the codeserver addon to your deployment.
 This guide will not cover every aspect of options available to Homepage. For more information, please visit the following links:
 
@@ -74,7 +74,7 @@ ingress:
     integrations:
       homepage:
         enabled: true
-        group: "Arr"          
+        group: "Arr"
         weight: 1
         widget:
           custom:

charts/stable/minecraft-router/docs/how-to.md

@@ -17,4 +17,4 @@ mcrouter:
       - ${SERVER1_URL}=minecraft-java.minecraft-java.svc.cluster.local:25565
       - ${SERVER2_URL}=truecharts-mcserver-minecraft-java.truecharts-mcserver.svc.cluster.local:25565
       - ${SERVER3_URL}=kidsplayground-server-minecraft-java.kidsplayground-server.svc.cluster.local:25565
-```` 
+````

charts/stable/minio/docs/installation_notes.md

@@ -5,7 +5,7 @@ title: Installation Notes
 :::caution
 
 There is only one persistence configured in the standard template. Which is used to store the config of minio and is mounted to `/data`.
-If you want the backup data on a different PVC/NFS share/.... Configure an extra persistence in your Helm values. 
+If you want the backup data on a different PVC/NFS share/.... Configure an extra persistence in your Helm values.
 
 When minio is used to store backup data like your VOLSYNC data for example, make sure this deployment is not on the same server as where all other charts are running.
 
@@ -22,4 +22,4 @@ This is the minimal required settings for deployment via environment variables:
 
 - `MINIO_ROOT_USER` and `MINIO_ROOT_PASSWORD` represent the username and password used to login to minio.
 
-For detailed information regarding all environment variables, check documention upstream. 
+For detailed information regarding all environment variables, check documention upstream.

charts/stable/nzbget/Chart.yaml

@@ -30,8 +30,8 @@ maintainers:
 name: nzbget
 sources:
   - https://ghcr.io/elfhosted/nzbget
+  - https://github.com/nzbgetcom/nzbget
   - https://github.com/truecharts/charts/tree/master/charts/stable/nzbget
   - https://nzbget.net/
-  - https://github.com/nzbgetcom/nzbget
 type: application
 version: 24.6.2

charts/stable/organizr/docs/forward_auth.md

@@ -56,7 +56,7 @@ middlewares:
       address: http://organizr.organizr.svc.cluster.local:10022/api/v2/auth?group=0
       trustForwardHeader: true
     #OPTIONAL
-    - name: organizr-guest    
+    - name: organizr-guest
       address: http://organizr.organizr.svc.cluster.local:10022/api/v2/auth?group=999
       trustForwardHeader: true
     #OPTIONAL, CUSTOM

charts/stable/pihole/docs/split-dns.md

@@ -47,5 +47,5 @@ env:
 
 ## Configure Router
 
-1. Configure your router to use your PiHole DNS when configuring DNS clients. You will need to consult your router manual for this as each router is different. 
+1. Configure your router to use your PiHole DNS when configuring DNS clients. You will need to consult your router manual for this as each router is different.
-In above example, the router should be configured to use 192.168.1.221 as the DNS server. 
+In above example, the router should be configured to use 192.168.1.221 as the DNS server.