UI update planning complete

docs/ui/entities/person/acceptance-criteria.md

@@ -132,7 +132,7 @@ This checklist does not cover:
 
 ### QG-1 Separation of intent and implementation
 1. UX intent remains in user-journey.md
-2. current versus target implementation mapping remains in schema-mapping.md
+2. Current versus target implementation mapping remains in schema-mapping.md
 
 ### QG-2 Traceability
 1. Each accepted behavior maps to at least one future UI action or service call path

docs/ui/entities/person/user-journey.md

@@ -131,10 +131,10 @@ Date handling rule:
 ## 7. Submission Behavior
 
 On submit:
-1. system validates required fields
-2. system creates Person record
-3. system returns user to Person detail page
-4. system shows success message
+1. The system validates required fields
+2. The system creates the Person record
+3. The system returns the user to the Person detail page
+4. The system shows a success message
 
 Recommended transactional behavior:
 1. Person writes are atomic
@@ -143,16 +143,16 @@ Recommended transactional behavior:
 ## 8. Expected Result After Success
 
 After successful creation:
-1. user sees Person detail page for the new record
+1. The user sees the Person detail page for the new record
 2. full_name is visible in the header or summary
 3. empty Related Documents section is shown if no links exist
-4. user can proceed to link this person from Document workflows
+4. The user can proceed to link this person from Document workflows
 
 ## 9. Expected Result After Failure
 
 If creation fails:
-1. show clear error message
-2. show field-level feedback for validation failures
+1. Show a clear error message
+2. Show field-level feedback for validation failures
 3. preserve entered data where possible
 4. do not show false success messaging
 
@@ -176,7 +176,7 @@ The Person detail page should show:
 ### 10.3 Read Empty State
 
 If no linked documents exist:
-1. show No linked documents yet
+1. Show No linked documents yet
 2. provide guidance to link from Document workflow
 
 ## 11. Update Person Journey
@@ -217,9 +217,9 @@ On save:
 
 ### 11.4 Update Failure Behavior
 
-1. show clear error feedback
+1. Show clear error feedback
 2. preserve form state where possible
-3. allow retry
+3. Allow retry
 
 ## 12. Delete Person Journey
 
@@ -238,12 +238,12 @@ Delete is blocked when:
 ### 12.3 Blocked Delete UX
 
 1. explain that linked Document relationships exist
-2. show link count or list
+2. Show link count or list
 3. provide cleanup path
 
 ### 12.4 Allowed Delete UX
 
-1. show confirmation dialog
+1. Show a confirmation dialog
 2. confirm permanent action
 3. delete Person
 4. return to Person list with success message