fix build errors

Author: captainbrosset

microsoft-edge/web-platform/release-notes/133.md

@@ -5,7 +5,7 @@ author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: conceptual
 ms.service: microsoft-edge
-ms.date: 
+ms.date: 01/31/2025
 ---
 # Edge 133 web platform release notes (Feb 2025)
 
@@ -198,11 +198,11 @@ The maxInterStageShaderComponents limit is being removed due to a combination of
 
 ###### Remove `<link rel=prefetch>` five-minute rule
 
-Previously, when a resource was prefetched using <link rel=prefetch>, we ignored its cache semantics (namely max-age and no-cache) for the first use within 5 minutes, to avoid refetching. Now, we remove this special case and use normal HTTP cache semantics.
+Previously, when a resource was prefetched using `<link rel=prefetch>`, we ignored its cache semantics (namely max-age and no-cache) for the first use within 5 minutes, to avoid refetching. Now, we remove this special case and use normal HTTP cache semantics.
 
-This means web developers need to include appropriate caching headers (i.e. Cache-Control or Expires) to see benefits from <link rel=prefetch>.
+This means web developers need to include appropriate caching headers (i.e. Cache-Control or Expires) to see benefits from `<link rel=prefetch>`.
 
-This also affects the nonstandard <link rel=prerender>.
+This also affects the nonstandard `<link rel=prerender>`.
 
 This fixes a bug with speculation rules prefetch, where non-2xx responses were cached. However, it does not start requiring caching headers for speculation rules prefetch, since they are intended for navigational prefetching and thus have different caching needs than the normal HTTP cache.