docs(cloudflared): helmify docs (#32743)

**Description**
<!--
helmify docs
-->
⚒️ Fixes  # <!--(issue)-->

**⚙️ Type of change**

- [ ] ⚙️ Feature/App addition
- [ ] 🪛 Bugfix
- [ ] ⚠️ Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] 🔃 Refactor of current code
- [ x] 📜 Documentation Changes

**🧪 How Has This Been Tested?**
<!--
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
-->

**📃 Notes:**
<!-- Please enter any other relevant information here -->

**✔️ Checklist:**

- [ ] ⚖️ My code follows the style guidelines of this project
- [ ] 👀 I have performed a self-review of my own code
- [ ] #️⃣ I have commented my code, particularly in hard-to-understand
areas
- [x ] 📄 I have made changes to the documentation
- [ ] 🧪 I have added tests to this description that prove my fix is
effective or that my feature works
- [ ] ⬆️ I increased versions for any altered app according to semantic
versioning
- [ x] I made sure the title starts with `feat(chart-name):`,
`fix(chart-name):`, `chore(chart-name):`, `docs(chart-name):` or
`fix(docs):`

**➕ App addition**

If this PR is an app addition please make sure you have done the
following.

- [ ] 🖼️ I have added an icon in the Chart's root directory called
`icon.png`

---

_Please don't blindly check all the boxes. Read them and only check
those that apply.
Those checkboxes are there for the reviewer to see what is this all
about and
the status of this PR with a quick glance._

charts/stable/cloudflared/docs/installation_notes.md

@@ -26,7 +26,7 @@ Cloudflare’s content delivery network (the “CDN”) Service can be used to c
 ![cf-tunnel-token.png](./img/cf-tunnel-token.png)
 
 - Set the `token` with **your** tunnel's token. the tunnel ID will **NOT** work.
-- Now you can manage the tunnel via cloudflare dash by setting a private network or create ingress rules for your services and domain, explained in [Setting up individial apps](#setting-up-individual-apps)
+- Now you can manage the tunnel via cloudflare dash by setting a private network or create ingress rules for your services and domain, explained in [Setting up individial charts](#setting-up-individual-charts)
 
 ![cf-tunnel-hostname](./img/cf-tunnel-hostname.png)
 
@@ -38,21 +38,21 @@ Cloudflare’s content delivery network (the “CDN”) Service can be used to c
 
 :::
 
-## Setting up individual apps
+## Setting up individual charts
 
 ### Using traefik
 
-If you've set up your apps with traefik, you need to set up two public hostnames
+If you've set up your charts with traefik, you need to set up two public hostnames
 
 - Set `subdomain` to a sub domain (can be left blank to use the root domain)
 - Set `domain` to your domain
 - Set `type` to `HTTPS`
-- Set `URL` to your traefik URL, usually `traefik-tcp.ix-traefik.svc.cluster.local:443` (make sure the port is the same as the port you specified in traefik config)
-- Under `Additional app settings` > `TLS`, set `Origin Server Name` to your domain (This needs to **match** what you have set for the sub and root domain; ex `someapp.somedomain.com`).
+- Set `URL` to your traefik URL, usually `traefik-tcp.traefik.svc.cluster.local:443` (make sure the port is the same as the port you specified in traefik config)
+- Under `Additional application settings` > `TLS`, set `Origin Server Name` to your domain (This needs to **match** what you have set for the sub and root domain; example: `chartname.somedomain.com`).
 
-Then you need to do the same to set up the subdomain for each app you want to expose, using the same subdomain you specified in the app's ingress settings as follows:
+Then you need to do the same to set up the subdomain for each chart you want to expose, using the same subdomain you specified in the charts ingress section as follows:
 
-![cloudflare-setup](./img/cloudflare-setup2.png)
+![cloudflare-setup](./img/cloudflare-setup.png)
 
 :::danger[No TLS Verify]
 
@@ -62,4 +62,4 @@ Please refrain from enabling the "No TLS Verify" option, as doing so will disabl
 
 ### Without traefik
 
-If you've not set up traefik and ingress, and exposing the ports using the normal loadbalancer, you only need to set up each app individually, and set `URL` to `<TrueNAS Local IP>:<PORT of app>` or cluster app url for each app.
+If you've not set up traefik and ingress, and exposing the ports using the normal loadbalancer, you only need to set up each chart individually, and set `URL` to `<LoadBalancerIP>:<PORT>` or cluster-url for each chart.