Review remarks 3

Co-authored-by: Dipesh Rawat <[email protected]>

Author: mimowo

content/en/blog/_posts/2025-04-23-jobs-backofflimitperindex-goes-ga.md

@@ -1,9 +1,9 @@
 ---
 layout: blog
-title: "Kubernetes 1.33: Job's Backoff Limit Per Index Goes GA"
+title: "Kubernetes v1.33: Job's Backoff Limit Per Index Goes GA"
 date: 2025-04-23
 draft: true
-slug: kubernetes-1-33-jobs-backoff-limit-per-index-goes-ga
+slug: kubernetes-v1-33-jobs-backoff-limit-per-index-goes-ga
 author: >
   [Michał Woźniak](https://github.com/mimowo) (Google)
 ---
@@ -26,7 +26,7 @@ However, for workloads where every index is considered independent, like
 [embarassingly parallel](https://en.wikipedia.org/wiki/Embarrassingly_parallel)
 workloads - the `spec.backoffLimit` field is often not flexible enough.
 For example, you may choose to run multiple suites of integration tests by
-representing each suite as an index within an [Indexed Job](https://kubernetes.io/docs/tasks/job/indexed-parallel-processing-static/).
+representing each suite as an index within an [Indexed Job](/docs/tasks/job/indexed-parallel-processing-static/).
 In that setup, a fast-failing index  (test suite) is likely to consume your
 entire budget for tolerating Pod failures, and you might not be able to run the
 other indexes.