pkgs.k8s.io: fix nits from previous PRs

Signed-off-by: Marko Mudrinić <[email protected]>

Author: xmudrii

content/en/blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md

@@ -50,7 +50,9 @@ _(updated on January 12, 2024 and March 26, 2024)_
 - Given that no new releases will be published to the legacy repositories after
   the September 13, 2023 cut-off point, you will not be able to upgrade to any patch or minor
   release made from that date onwards if you don't migrate to the new Kubernetes package repositories.
-  That said, we recommend migrating to the new Kubernetes package repositories **as soon as possible**.
+  ~~That said, we recommend migrating to the new Kubernetes package repositories **as soon as possible**.~~
+  Migrating to the new Kubernetes package repositories is required to consume the official Kubernetes
+  packages.
 - **The new Kubernetes package repositories contain packages beginning with those
   Kubernetes versions that were still under support when the community took
   over the package builds. This means that the new package repositories have Linux packages for all

content/en/blog/_posts/2023-08-31-legacy-package-repository-deprecation/index.md

@@ -129,10 +129,9 @@ future. However, the Kubernetes project can't provide _any_ guarantees on how lo
 is that going to be. The deprecated legacy repositories, and their contents, might
 be removed at any time in the future and without a further notice period.~~
 
-~~**UPDATE**: The legacy packages are expected to go away by the end of February 2024.~~
-
-The Kubernetes project **strongly recommends** migrating to the new community-owned
-repositories **as soon as possible**.
+~~The Kubernetes project **strongly recommends** migrating to the new community-owned
+repositories **as soon as possible**.~~ Migrating to the new package repositories is
+required to consume the official Kubernetes packages.
 
 Given that no new releases will be published to the legacy repositories **after the September 13, 2023**
 cut-off point, **you will not be able to upgrade to any patch or minor release made from that date onwards.**