Final review edits

flang-msft · flang-msft · commit 5a6346750342 · 2024-06-03T15:08:07.000-07:00
diff --git a/articles/azure-cache-for-redis/cache-whats-new.md b/articles/azure-cache-for-redis/cache-whats-new.md
@@ -13,52 +13,43 @@ ms.date: 05/20/2024
 
 # What's New in Azure Cache for Redis
 
-## May 2024
-
-### Azure Functions
+## June 2024
 
-Using Azure Cache for Redis with Azure Functions to create optimized serverless and event-driven architectures is now in General Availability (GA).
+### .NET Output cache and HybridCache
 
-For more information, see [Overview of Azure functions for Azure Cache for Redis](/azure/azure-functions/functions-bindings-cache).
+Using Azure Cache for Reds as output cache was introduced in .NET 8 in November 2023. Output Caching saves rendered web pages to improve performance, resilience, and reduce cost through server resource utilization. You can use Redis as a built-in output cache store in .NET 8. For more information on using Redis as an output cache, see [Output caching middleware in ASP.NET Core](/aspnet/core/performance/caching/output#redis-cache)
 
-### Microsoft Entra ID
+ASP.NET Core's support for distributed caching is broadening _.NET 9 Preview 4_ for .NET 9 a new _HybridCache_ API. _HybridCache_ augments the existing `IDistributedCache` support in ASP.NET Core with new capabilities, including multi-tier storage, with a limited in-process L1 cache supplemented by a separate (usually larger) out-of-process L2 cache. The hybrid approach to cache storage provides you with two advantages: most fetches are served efficiently from L1, but cold-start and data you access infrequently use L2. Using L2 for data you access less frequently doesn't over-utilize the underlying backend.
 
-Support Microsoft Entra ID for authentication and role-based access control across regions that support Azure Cache for Redis is now in General Availability (GA).
+For more information and downloading, see [.NET 9 Preview 4](https://dotnet.microsoft.com/en-us/download/dotnet/9.0)
 
-For more information, see [Use Microsoft Entra ID for cache authentication](cache-azure-active-directory-for-authentication.md).
+_HybridCache_ also includes:
 
-### .NET Output Cache and Hybrid Cache
-
-<!-- If this came out in November 2023, shouldn't it be in that section? -->
-
-Using Azure Cache for Reds as output cache was introduced in .NET 8 in November 2023. The Web Output Caching saves rendered web pages to improve performance, resilience, and reduce cost from server resource utilization. Redis has been implemented as built-in output cache store in .NET 8.
-
-<!--  What is "Web Output Caching" referring to? -->
+- _stampede protection_ to prevent parallel fetches of the same data
+- configurable serialization
+- simplifying the API usage for common scenarios
 
-For more information on using Redis as an output cache, see [Output caching middleware in ASP.NET Core](/aspnet/core/performance/caching/output#redis-cache)
+For more information, see the [HybridCache library](/aspnet/core/release-notes/aspnetcore-9.0#new-hybridcache-library).
 
-ASP.NET Core's support for distributed caching is getting an upgrade with the new _HybridCache_ API. _HybridCache_ augments the existing `IDistributedCache` support in ASP.NET Core with new capabilities, including multi-tier storage, with a limited in-process (L1) cache supplemented by a separate (usually larger) out-of-process (L2) cache. The hybrid approach to cache storage provides you with two advantages, where most fetches are served efficiently from L1, but cold-start and data you access less frequently doesn't over utilize the underlying backend because hybrid uses L2 for that.
+### Connection Auditing
 
-<!-- the phrase  "less-frequently-accessed data still doesn't hammer the underlying backend" is too colloquial and doesn't translate well as an idiom -->
+Connection auditing is GA for all SKUs, and you can configure an Azure Policy to audit or enforce specific policies about private endpoints and public network access with your caches. Azure Cache for Redis doesn't provide a built-in policy, but you can author a custom policy to enforce that private endpoints are enabled.
 
-<!-- is getting an upgrade? Is it happening now? Why are we talking about this feature if it isn't available? -->
+For more information, see [Manage network policies for private endpoints](/azure/private-link/disable-private-endpoint-network-policy).
 
-HybridCache also includes:
+## May 2024
 
-- _stampede protection_ to prevent parallel fetches of the same data
-- configurable serialization
-- simplifying the API usage for common scenarios
+### Azure Functions
 
-For more information, see the [HybridCache library](/aspnet/core/release-notes/aspnetcore-9.0#new-hybridcache-library).
+Using Azure Cache for Redis with Azure Functions to create optimized serverless and event-driven architectures is now in General Availability (GA).
 
-### Connection Auditing
+For more information, see [Overview of Azure functions for Azure Cache for Redis](/azure/azure-functions/functions-bindings-cache).
 
-Connection auditing is GA for all SKUs.
-<!-- When did it GA? we can put it in the month where it GA'd. This isn't a Redis feature, right  or do you mean are we announcing that user can configure this for Redis, what is the Redis connection-->
+### Microsoft Entra ID
 
-You can configure an Azure Policy to audit or enforce specific policies about private endpoints and public network access. There isn't currently a built-in policy for doing this, but you can author a custom policy to enforce that private endpoints are enabled.
+Support Microsoft Entra ID for authentication and role-based access control across regions that support Azure Cache for Redis is now in General Availability (GA).
 
-For more information, see [Manage network policies for private endpoints](/azure/private-link/disable-private-endpoint-network-policy).
+For more information, see [Use Microsoft Entra ID for cache authentication](cache-azure-active-directory-for-authentication.md).
 
 ## April 2024
 
@@ -80,7 +71,7 @@ For more information, see [What are the configuration settings for the TLS proto
 
 ## October 2023
 
-### Flush data operation for Basic, Standard and Premium Caches (preview)
+### Flush data operation for Basic, Standard, and Premium Caches (preview)
 
 Basic, Standard, and Premium tier caches now support a built-in _flush_ operation that can be started at the control plane level. Use the _flush_ operation with your cache executing the `FLUSH ALL` command through Portal Console or _redis-cli_.
 
