Fix a mistake with the last commit to update the docs

Signed-off-by: Darkfella91 <[email protected]>

docs/spec/v1beta3/providers.md

@@ -922,12 +922,6 @@ and [TLS certificates](#tls-certificates).
 To configure a Provider for Prometheus Alertmanager, you can authenticate using Basic Authentication or a Bearer Token. 
 Both authentication methods are supported, and you can choose the one that best fits your setup.
 
-To configure a Provider for Prometheus Alertmanager, create a Secret with [the
-`address`](#address-example) set to the Prometheus Alertmanager [HTTP API
-URL](https://prometheus.io/docs/alerting/latest/https/#http-traffic)
-including Basic Auth credentials, and a `alertmanager` Provider with a [Secret
-reference](#secret-reference).
-
 Basic Authentication: 
 Create a Secret with [the `address`](#address-example) set to the Prometheus Alertmanager [HTTP API
 URL](https://prometheus.io/docs/alerting/latest/https/#http-traffic)
@@ -955,7 +949,30 @@ stringData:
     address: https://username:password@<alertmanager-url>/api/v2/alerts/"
 ```
 Bearer Token Authentication:
-Create a Secret with [the `token`](#token-example)
+Create a Secret with [the `token`](#token-example), and a `alertmanager` Provider with a [Secret
+reference](#secret-reference) and the address set directly in the spec.address field.
+
+```yaml
+---
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
+kind: Provider
+metadata:
+  name: alertmanager
+  namespace: default
+spec:
+  type: alertmanager
+  address: <alertmanager-url>/api/v2/alerts/
+  secretRef:
+    name: alertmanager-token
+---
+apiVersion: v1
+kind: Secret
+metadata:
+  name: alertmanager-token
+  namespace: default
+stringData:
+    token: <token>
+```
 
 ##### Webex