Skip to content

Commit 81eb98a

Browse files
committed
Updates
1 parent e1e6f00 commit 81eb98a

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

aspnetcore/blazor/call-web-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ In-memory distributed token caches are created when calling <xref:Microsoft.Iden
9898
Production web apps and web APIs should use a production distributed token cache (for example: [Redis](https://redis.io/), [Microsoft SQL Server](https://www.microsoft.com/sql-server), [Microsoft Azure Cosmos DB](https://azure.microsoft.com/products/cosmos-db)).
9999

100100
> [!NOTE]
101-
> For local testing and development on a single machine, you can use in-memory token caches instead of distributed token caches:
101+
> For local development and testing on a single machine, you can use in-memory token caches instead of distributed token caches:
102102
>
103103
> ```csharp
104104
> builder.Services.AddInMemoryTokenCaches();

aspnetcore/blazor/security/blazor-web-app-with-entra.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -698,7 +698,7 @@ In-memory distributed token caches are created when calling <xref:Microsoft.Iden
698698
Production web apps and web APIs should use a production distributed token cache (for example: [Redis](https://redis.io/), [Microsoft SQL Server](https://www.microsoft.com/sql-server), [Microsoft Azure Cosmos DB](https://azure.microsoft.com/products/cosmos-db)).
699699

700700
> [!NOTE]
701-
> For local testing and development on a single machine, you can use in-memory token caches instead of distributed token caches:
701+
> For local development and testing on a single machine, you can use in-memory token caches instead of distributed token caches:
702702
>
703703
> ```csharp
704704
> builder.Services.AddInMemoryTokenCaches();

0 commit comments

Comments
 (0)