Skip to content

Commit e33a3e6

Browse files
committed
Refactor compliance requirements section for clarity and consistency; update error handling pattern heading for uniformity
1 parent 35f3018 commit e33a3e6

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

learn-pr/wwl-data-ai/design-implement-sql-solutions-ai-assisted-tools/includes/3-interpret-security-impact.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Your organization might have specific policies about AI tool usage, especially w
2121

2222
**Data classification**: Does your database contain personally identifiable information (PII), financial records, healthcare data, or other regulated information? Some organizations restrict AI tool usage for databases containing sensitive data classifications.
2323

24-
**Compliance requirements**: Are you subject to GDPR, HIPAA, SOC 2, or other compliance frameworks? Review whether using cloud-based AI services aligns with your compliance obligations.
24+
**Compliance requirements**: Are you subject to any compliance frameworks? Review whether using cloud-based AI services aligns with your compliance obligations.
2525

2626
**Intellectual property**: Does your organization have policies about code or schema information being processed by external AI services? Some proprietary database designs might be considered trade secrets.
2727

learn-pr/wwl-data-ai/design-implement-sql-solutions-ai-assisted-tools/includes/6-create-configure-copilot-instruction-files.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ To get the most out of custom instruction files, follow these best practices:
139139
Example of a specific, example-driven instruction:
140140

141141
```markdown
142-
## Error Handling Pattern
142+
## Error handling pattern
143143

144144
Always use this error handling pattern in stored procedures:
145145

0 commit comments

Comments
 (0)