corrected markdown ordered listing (#35914)

Author: JaredMSFT

aspnetcore/performance/caching/distributed.md

@@ -27,7 +27,7 @@ When cached data is distributed, the data:
 * Survives server restarts and app deployments.
 * Doesn't use local memory.
 
-Distributed cache configuration is implementation specific. This article describes how to configure SQL Server and Redis distributed caches. Third party implementations are also available, such as [NCache](http://www.alachisoft.com/ncache/aspnet-core-idistributedcache-ncache.html) ([NCache on GitHub](https://github.com/Alachisoft/NCache)), Cosmos DB, and Postgres. Regardless of which implementation is selected, the app interacts with the cache using the <xref:Microsoft.Extensions.Caching.Distributed.IDistributedCache> interface.
+Distributed cache configuration is implementation specific. This article describes how to configure SQL Server, Redis, or Postgres distributed caches. Third party implementations are also available, such as [NCache](http://www.alachisoft.com/ncache/aspnet-core-idistributedcache-ncache.html) ([NCache on GitHub](https://github.com/Alachisoft/NCache)), Cosmos DB, and Postgres. Regardless of which implementation is selected, the app interacts with the cache using the <xref:Microsoft.Extensions.Caching.Distributed.IDistributedCache> interface.
 
 [View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/performance/caching/distributed/samples/) ([how to download](xref:index#how-to-download-a-sample))
 
@@ -166,7 +166,7 @@ builder.Services.AddDistributedPostgresCache(options => {
 var app = builder.Build();
 ```
 
-3. Use the Cache
+2. Use the Cache
 
 ```csharp
 public class MyService {

aspnetcore/performance/caching/distributed/includes/distributed5.md

@@ -145,7 +145,7 @@ builder.Services.AddDistributedPostgresCache(options => {
 var app = builder.Build();
 ```
 
-3. Use the Cache
+2. Use the Cache
 
 ```csharp
 public class MyService {

aspnetcore/performance/caching/distributed/includes/distributed6-7.md

@@ -148,7 +148,7 @@ builder.Services.AddDistributedPostgresCache(options => {
 var app = builder.Build();
 ```
 
-3. Use the Cache
+2. Use the Cache
 
 ```csharp
 public class MyService {

aspnetcore/performance/caching/hybrid.md

@@ -190,7 +190,7 @@ For more information, see the [HybridCache serialization sample app](https://git
 
 ## Cache storage
 
-By default `HybridCache` uses <xref:System.Runtime.Caching.MemoryCache> for its primary cache storage. Cache entries are stored in-process, so each server has a separate cache that is lost whenever the server process is restarted. For secondary out-of-process storage, such as Redis or SQL Server, `HybridCache` uses [the configured `IDistributedCache` implementation](xref:performance/caching/distributed), if any. But even without an `IDistributedCache`implementation, the `HybridCache` service still provides in-process caching and [stampede protection](https://en.wikipedia.org/wiki/Cache_stampede).
+By default `HybridCache` uses <xref:System.Runtime.Caching.MemoryCache> for its primary cache storage. Cache entries are stored in-process, so each server has a separate cache that is lost whenever the server process is restarted. For secondary out-of-process storage, such as Redis, SQL Server, or Postgres, `HybridCache` uses [the configured `IDistributedCache` implementation](xref:performance/caching/distributed), if any. But even without an `IDistributedCache`implementation, the `HybridCache` service still provides in-process caching and [stampede protection](https://en.wikipedia.org/wiki/Cache_stampede).
 
 > [!NOTE]
 > When invalidating cache entries by key or by tags, they're invalidated in the current server and in the secondary out-of-process storage. However, the in-memory cache in other servers isn't affected.