Update Based on Comments - Dec 5

content/en/blog/_posts/2023-12-15-volume-attributes-class/index.md

@@ -8,7 +8,7 @@ slug: kubernetes-1-29-volume-attributes-class
 **Author**: Sunny Song (Google)
 
 The v1.29 release of Kubernetes introduced an alpha feature to support modifying a volume
-by changing VolumeAttributesClassName that was assigned to a PersistentVolumeClaim (PVC).
+by changing the `volumeAttributesClassName` that was specified for a PersistentVolumeClaim (PVC).
 With the feature enabled, Kubernetes can handle updates of volume attributes other than capacity.
 Allowing volume attributes to be changed without managing it through different
 provider's APIs directly simplifies the current flow.
@@ -54,7 +54,7 @@ in the `kube-controller-manager` and the `kube-apiserver`. Use the `--feature-ga
 It also requires that the CSI driver has implemented the ModifyVolume API.
 
 
-### User Flow
+### User flow
 
 If you would like to see the feature in action and verify it works fine in your cluster, here's what you can try:
 
@@ -65,10 +65,10 @@ If you would like to see the feature in action and verify it works fine in your
 apiVersion: storage.k8s.io/v1
 kind: StorageClass
 metadata:
-  name: csi-sc-example
+   name: csi-sc-example
 provisioner: pd.csi.storage.gke.io
 parameters:
-  disk-type: "hyperdisk-balanced"
+   disk-type: "hyperdisk-balanced"
 volumeBindingMode: WaitForFirstConsumer
 ```
 
@@ -78,11 +78,11 @@ volumeBindingMode: WaitForFirstConsumer
 apiVersion: storage.k8s.io/v1alpha1
 kind: VolumeAttributesClass
 metadata:
-  name: silver
+   name: silver
 driverName: pd.csi.storage.gke.io
 parameters:
-  provisioned-iops: "3000"
-  provisioned-throughput: "50"
+   provisioned-iops: "3000"
+   provisioned-throughput: "50"
 ```
 
 
@@ -92,21 +92,21 @@ parameters:
 apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
-  name: test-pv-claim
+   name: test-pv-claim
 spec:
-  storageClassName: csi-sc-example
-  volumeAttributesClassName: silver
-  accessModes:
-    - ReadWriteOnce
-  resources:
-    requests:
-      storage: 64Gi
+   storageClassName: csi-sc-example
+   volumeAttributesClassName: silver
+   accessModes:
+      - ReadWriteOnce
+   resources:
+      requests:
+         storage: 64Gi
 ```
 
 
 3. Verify that the PersistentVolumeClaim is now provisioned correctly with:
 
-```yaml
+```
 kubectl get pvc
 ```
 
@@ -117,11 +117,11 @@ kubectl get pvc
 apiVersion: storage.k8s.io/v1alpha1
 kind: VolumeAttributesClass
 metadata:
-  name: gold
+   name: gold
 driverName: pd.csi.storage.gke.io
 parameters:
-  iops: "4000"
-  throughput: "60"
+   iops: "4000"
+   throughput: "60"
 ```
 
 
@@ -131,22 +131,21 @@ parameters:
 apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
-  name: test-pv-claim
+   name: test-pv-claim
 spec:
-  storageClassName: csi-sc-example
-  volumeAttributesClassName: gold
-  accessModes:
-    - ReadWriteOnce
-  resources:
-    requests:
-      storage: 64Gi
-
+   storageClassName: csi-sc-example
+   volumeAttributesClassName: gold
+   accessModes:
+      - ReadWriteOnce
+   resources:
+      requests:
+         storage: 64Gi
 ```
 
 
 6. Verify that PersistentVolumeClaims has the updated VolumeAttributesClass parameters with:
 
-```yaml
+```
 kubectl describe pvc <PVC_NAME>
 ```
 
@@ -155,13 +154,13 @@ kubectl describe pvc <PVC_NAME>
 * See the [VolumeAttributesClass KEP](https://kep.k8s.io/3751) for more information on the design
 * You can view or comment on the [project board](https://github.com/orgs/kubernetes-csi/projects/72) for VolumeAttributesClass
 * In order to move this feature towards beta, we need feedback from the community,
-so here's a call to action: add support to the CSI drivers, try out this feature,
-consider how it can help with problems that your users are having…
+  so here's a call to action: add support to the CSI drivers, try out this feature,
+  consider how it can help with problems that your users are having…
 
 
 ## Getting involved
 
-We always welcome new contributors. So, if you would like to get involved, you can join our [Kubernetes Storage Special-Interest-Group](https://github.com/kubernetes/community/tree/master/sig-storage) (SIG).
+We always welcome new contributors. So, if you would like to get involved, you can join our [Kubernetes Storage Special Interest Group](https://github.com/kubernetes/community/tree/master/sig-storage) (SIG).
 
 If you would like to share feedback, you can do so on our [public Slack channel](https://app.slack.com/client/T09NY5SBT/C09QZFCE5).