fix typo

Author: vvolkl

_gsocblogs/2024/blog_ContainerizeCBACK_YashRajSingh.md

@@ -137,7 +137,7 @@ We explored two approaches for mounting the necessary storage:
 - A storage class was defined in the Kubernetes cluster to facilitate this dynamic provisioning.
 - When the Scheduler Agent creates a job, it would also create a corresponding PVC, which would request a volume from the storage class and automatically mount it to the job pod.
 
- While testing dynamic provisioning, we faced a significant limitation regarding subvolume groups. For instance, if we intended to mount a pod to the root of the Ceph cluster e.g `/cephfs-miniflax`, the provisioner would only allow for the creation of a subvolume tied into a subvolumegroup instead. Therefore, if a job was set to operate on a specific path like `/cephfs-miniflax/volumes/_nogroup/miniflax_snaps/zgoggins` the pod would actually attempt to mount to a root path like `/cephfs-miniflax/<subvolume-group-name>/<dynamic-id-forsubvolume>` and it wasn't possible to overide to mount to an arbitrary path. This meant the scheduler could not locate the specified source path, leading to complications in job execution.
+ While testing dynamic provisioning, we faced a significant limitation regarding subvolume groups. For instance, if we intended to mount a pod to the root of the Ceph cluster e.g `/cephfs-miniflax`, the provisioner would only allow for the creation of a subvolume tied into a subvolumegroup instead. Therefore, if a job was set to operate on a specific path like `/cephfs-miniflax/volumes/_nogroup/miniflax_snaps/zgoggins` the pod would actually attempt to mount to a root path like `/cephfs-miniflax/<subvolume-group-name>/<dynamic-id-forsubvolume>` and it wasn't possible to override to mount to an arbitrary path. This meant the scheduler could not locate the specified source path, leading to complications in job execution.
 
 2. **Static Provisioning**: