Apply suggestions from code review

Co-authored-by: Jun Lee <[email protected]>

Author: garvit-gupta

src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx

@@ -17,7 +17,7 @@ This document provides details around any transition steps that may be needed to
 
 Legacy Vectorize (V1) indexes are on a deprecation path. Support for these indexes would be limited and their usage is not recommended for any production workloads.
 
-Furthemore, the creation of legacy Vectorize indexes will be blocked by December 2024. Other operations will be unaffected and will remain functional.
+Furthermore, you will no longer be able to create legacy Vectorize indexes by December 2024. Other operations will be unaffected and will remain functional.
 
 Additionally, the new Vectorize (V2) indexes can operate at a significantly larger scale (with a capacity for multi-million vectors), and provide faster performance. Please review the [Limits](/vectorize/platform/limits/) page to understand the latest capabilities supported by Vectorize.
 

src/content/partials/vectorize/vectorize-legacy.mdx

@@ -6,7 +6,7 @@
 
 Please use the `wrangler vectorize --deprecated-v1` flag to create, get, list, delete and insert vectors into legacy Vectorize V1 indexes.
 
-Please note that the creation of legacy Vectorize indexes will be blocked by December 2024. Other operations will remain functional.
+Please note that by December 2024, you will not be able to create legacy Vectorize indexes. Other operations will remain functional.
 
 Refer to the [legacy transition](/vectorize/reference/transition-vectorize-legacy) page for more details on transitioning away from legacy indexes.