update

Author: mrbullwinkle

articles/ai-services/openai/concepts/assistants.md

@@ -45,14 +45,14 @@ We provide a walkthrough of the Assistants playground in our [quickstart guide](
 
 ## Assistants data access
 
-Currently, assistants, threads, messages, and files created for Assistants are scoped at the Azure OpenAI resource level. Therefore, anyone with access ot the Azure OpenAI resource or API key access is able to read/write assistants, threads, messages, and files.
+Currently, assistants, threads, messages, and files created for Assistants are scoped at the Azure OpenAI resource level. Therefore, anyone with access to the Azure OpenAI resource or API key access is able to read/write assistants, threads, messages, and files.
 
 We strongly recommend the following data access controls:
 
 - Implement authorization. Before performing reads or writes on assistants, threads, messages, and files, ensure that the end-user is authorized to do so.
 - Restrict Azure OpenAI resource and API key access. Carefully consider who has access to Azure OpenAI resources where assistants are being used and associated API keys.
 - Routinely audit which accounts/individuals have access to the Azure OpenAI resource. API keys and resource level access enable a wide range of operations including reading and modifying messages and files.
-- Enable [diagnostic settings](../how-to/monitoring.md#configure-diagnostic-settings) to allow long-term tracking of the Azure OpenAI resource's activity log.
+- Enable [diagnostic settings](../how-to/monitoring.md#configure-diagnostic-settings) to allow long-term tracking of certain aspects of the Azure OpenAI resource's activity log.
 
 ## See also