UI update planning complete

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

@@ -98,7 +98,7 @@ This checklist does not cover:
 
 ### UP-2 Revision validation
 1. revised_text cannot be saved as empty after trimming
-2. warning feedback is shown for invalid empty input
+2. Warning feedback is shown for invalid empty input
 
 ### UP-3 Successful revision save
 1. Given valid revision text
@@ -149,7 +149,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 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 UI action or service path

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

@@ -76,9 +76,9 @@ The user wants to start a transcription run by selecting the right Document and
 
 ### 5.2 Create Entry
 
-1. user opens the Jobs page
-2. user selects Create job
-3. system opens Job detail/create page in create mode
+1. The user opens the Jobs page
+2. The user selects Create job
+3. The system opens Job detail/create page in create mode
 
 ### 5.3 Create Inputs
 
@@ -93,9 +93,9 @@ The user wants to start a transcription run by selecting the right Document and
 
 ### 5.4 Source Handling Rules
 
-1. each uploaded file becomes a Source linked to the selected Document
-2. each created Source is linked to the Job through JobSource
-3. multi-file or folder uploads are processed alphabetically by original filename
+1. Each uploaded file becomes a Source linked to the selected Document
+2. Each created Source is linked to the Job through JobSource
+3. Multi-file or folder uploads are processed alphabetically by original filename
 4. upload_name stores the original filename
 5. stored filename uses UUID plus original extension in the form UUID.extension
 
@@ -124,7 +124,7 @@ On submit:
 
 Recommended transactional behavior:
 1. intended create writes should succeed or fail together
-2. user should not receive false success when required records fail
+2. The user should not receive false success when required records fail
 
 ### 5.7 Create Success Result
 
@@ -132,12 +132,12 @@ After successful create:
 1. job appears in Jobs list
 2. job detail shows selected Document and created source set
 3. status appears as queued or processing based on execution timing
-4. user can monitor progress and open page-level review
+4. The user can monitor progress and open page-level review
 
 ### 5.8 Create Failure Result
 
 If create fails:
-1. show clear error message
+1. Show clear error message
 2. preserve entered selections where possible
 3. keep retry path available
 4. do not show false success feedback
@@ -177,11 +177,11 @@ If no jobs exist:
 2. list shows Create job action
 
 If a job id is invalid or missing:
-1. show clear not found state
+1. Show clear not found state
 2. do not crash the page
 
 If a job has no source items due to failure:
-1. show clear warning state
+1. Show clear warning state
 2. keep recovery guidance visible
 
 ## 7. Job Status Lifecycle UX
@@ -199,23 +199,23 @@ The UI should map to model-backed job states:
 ### 7.2 In-Progress States
 
 When status is queued or processing:
-1. show active progress state
+1. Show active progress state
 2. keep detail page refresh-safe
 3. indicate that source-level results may still be arriving
 
 ### 7.3 Terminal States
 
 When status is completed:
-1. show completion success state
+1. Show completion success state
 2. direct user to revision workflow
 
 When status is partial_success:
-1. show mixed outcome state
+1. Show mixed outcome state
 2. identify failed pages
 3. guide user to review available successful pages and retry strategy
 
 When status is failed:
-1. show failure state with actionable message
+1. Show failure state with actionable message
 2. keep navigation and retry guidance available
 
 ## 8. Update Job Journey
@@ -243,9 +243,9 @@ On revision save:
 4. show success feedback
 
 On save failure:
-1. show clear error feedback
+1. Show clear error feedback
 2. preserve entered text where possible
-3. allow retry
+3. Allow retry
 
 ## 9. Delete and Retention Policy