Skip to content

Commit ee8f451

Browse files
committed
Acrolinx fixes
1 parent 6d2b1bb commit ee8f451

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

learn-pr/wwl-data-ai/responsible-ai-studio/includes/5-mitigate-harms.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The model layer consists of one or more generative AI models at the heart of you
1515

1616
Mitigations you can apply at the model layer include:
1717

18-
- Selecting a model that is appropriate for the intended solution use. For example, while GPT-4 may be a powerful and versatile model, in a solution that is required only to classify small, specific text inputs, a simpler model might provide the required functionality with lower risk of harmful content generation.
18+
- Selecting a model that's appropriate for the intended solution use. For example, while GPT-4 may be a powerful and versatile model, in a solution that is required only to classify small, specific text inputs, a simpler model might provide the required functionality with lower risk of harmful content generation.
1919
- *Fine-tuning* a foundational model with your own training data so that the responses it generates are more likely to be relevant and scoped to your solution scenario.
2020

2121
## 2: The *safety system* layer

learn-pr/wwl-data-ai/responsible-ai-studio/includes/6-operate-responsibly.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ After you map potential harms, develop a way to measure their presence, and impl
22

33
## Complete prerelease reviews
44

5-
Before releasing a generative AI solution, identify the various compliance requirements in your organization and industry and ensure the appropriate teams are given the opportunity to review the system and its documentation. Common compliance reviews include:
5+
Before releasing a generative AI solution, identify the various compliance requirements in your organization and industry and ensure the appropriate teams are provided with the opportunity to review the system and its documentation. Common compliance reviews include:
66

77
- Legal
88
- Privacy
@@ -18,5 +18,5 @@ A successful release requires some planning and preparation. Consider the follow
1818
- Create a *rollback plan* that defines the steps to revert the solution to a previous state if an incident occurs.
1919
- Implement the capability to immediately block harmful system responses when they're discovered.
2020
- Implement a capability to block specific users, applications, or client IP addresses in the event of system misuse.
21-
- Implement a way for users to provide feedback and report issues. In particular, enable users to report generated content as "inaccurate", "incomplete", "harmful", "offensive", or otherwise problematic.
21+
- Implement a way for users to provide feedback and report issues. In particular, enable users to report generated content as *inaccurate*, *incomplete*, *harmful*, *offensive*, or otherwise problematic.
2222
- Track telemetry data that enables you to determine user satisfaction and identify functional gaps or usability challenges. Telemetry collected should comply with privacy laws and your own organization's policies and commitments to user privacy.

0 commit comments

Comments
 (0)