Skip to content

Commit 41b1b8a

Browse files
committed
fix headings
Signed-off-by: Hannah Hunter <[email protected]>
1 parent 38e1a25 commit 41b1b8a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/aks/dapr.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ az k8s-extension create --cluster-type managedClusters \
130130

131131
Based on your environment (dev, test, or production), you can keep up-to-date with the latest stable Dapr versions.
132132

133-
### Choosing a release train
133+
#### Choosing a release train
134134

135135
When configuring the extension, you can choose to install Dapr from a particular release train. Specify one of the two release train values:
136136

@@ -160,7 +160,7 @@ You can disable auto-update by specifying the `--auto-upgrade-minor-version` par
160160
--auto-upgrade-minor-version true
161161
```
162162

163-
### Viewing the latest stable Dapr versions available
163+
#### Viewing the latest stable Dapr versions available
164164

165165
To upgrade to the latest Dapr version in a production environment, you need to manually upgrade. Start by viewing a list of the stable Dapr versions available to your managed AKS cluster. Run the following command:
166166

@@ -184,7 +184,7 @@ az k8s-extension extension-types list-versions-by-location --location westus --e
184184

185185
[Next, manually update Dapr to the latest stable version.](#targeting-a-specific-dapr-version)
186186

187-
### Targeting a specific Dapr version
187+
#### Targeting a specific Dapr version
188188

189189
> [!NOTE]
190190
> Dapr is supported with a rolling window, including only the current and previous versions. It is your operational responsibility to remain up to date with these supported versions. If you have an older version of Dapr, you may have to do intermediate upgrades to get to a supported version.

0 commit comments

Comments
 (0)