From 573f1dcb5cd1b1677dc0d7cb61cd2269f87dbbfd Mon Sep 17 00:00:00 2001 From: mrchatam Date: Fri, 11 Sep 2026 23:14:35 +0000 Subject: [PATCH] docs: fix 'allows to' grammar in ContentSafety sample README --- dotnet/samples/Demos/ContentSafety/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet/samples/Demos/ContentSafety/README.md b/dotnet/samples/Demos/ContentSafety/README.md index f0cc0f2f4c12..649c7c790f5e 100644 --- a/dotnet/samples/Demos/ContentSafety/README.md +++ b/dotnet/samples/Demos/ContentSafety/README.md @@ -4,7 +4,7 @@ This sample provides a practical demonstration of how to leverage [Semantic Kern [Azure AI Content Safety](https://learn.microsoft.com/en-us/azure/ai-services/content-safety/overview) detects harmful user-generated and AI-generated content in applications and services. Azure AI Content Safety includes text and image APIs that allow to detect material that is harmful. -[Prompt Shields](https://learn.microsoft.com/en-us/azure/ai-services/content-safety/quickstart-jailbreak) service allows to check your large language model (LLM) inputs for both User Prompt and Document attacks. +[Prompt Shields](https://learn.microsoft.com/en-us/azure/ai-services/content-safety/quickstart-jailbreak) service allows you to check your large language model (LLM) inputs for both User Prompt and Document attacks. Together with Semantic Kernel Prompt Filters, it's possible to define detection logic in dedicated place and avoid mixing it with business logic in applications.