Skip to content

fix(samples): correct text capitalisation on CC React App samples page (CAI-8463) - #738

Draft
mkesavan13 wants to merge 1 commit into
nextfrom
fix/CAI-8463-samples-page-copy-text-consistency
Draft

fix(samples): correct text capitalisation on CC React App samples page (CAI-8463)#738
mkesavan13 wants to merge 1 commit into
nextfrom
fix/CAI-8463-samples-page-copy-text-consistency

Conversation

@mkesavan13

@mkesavan13 mkesavan13 commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

COMPLETES #CAI-8463

This pull request addresses

Inconsistent capitalisation in copy text on the Contact Center Widgets samples page (`widgets-samples/cc/samples-cc-react-app/src/App.tsx`). Labels and headings used a mix of sentence-case and title-case, making the UI appear inconsistent.

by making the following changes

  • `"Contact Center Widgets in a React app"` → `"Contact Center Widgets in a React App"` (consistent title-case for "App")
  • `"Interaction preferences changes"` → `"Interaction Preferences Changes"` (title-case)
  • `"Your interaction preference is updated"` → `"Your Interaction Preference Is Updated"` (title-case)
  • `"Your access token: "` → `"Your Access Token: "` (title-case)

Change Type

  • Bug fix (non-breaking change which fixes an issue)

The following scenarios were tested

  • The testing is done with the amplify link
  • Manual visual inspection of the affected text strings confirms correct title-case rendering.
  • No logic changes; copy-only update to four string literals.

External Validation Required

AC Requirement Scope Details
AC-1 The CC React sample app's pre-init UI copy (page heading, fieldset legends, control/field labels, and interaction toast copy) follows one consistent Title Case convention, eliminating the mixed-case outliers — the heading reads 'Contact Center Widgets in a React App' (matching the page <title>) and the token field label reads 'Your Access Token:'. external The sample app (widgets-samples/cc/samples-cc-react-app) has no unit-test harness (package.json scripts are tsc build, webpack, eslint only). The tsc compile gate proves type-validity but not copy casing. Consistency of the static string literals is verified by manual source inspection against the Title Case baseline and the public/index.html <title>.

Contract Discovery Warnings

  • Manifest reference discovery capped at 100 strings

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Other - Please Specify: Claude Code (Anthropic)
  • This PR is related to
    • Defect fix

Checklist before merging

  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the testing document
  • I have tested the functionality with amplify link

Make sure to have followed the contributing guidelines before submitting.

Applies consistent title-case to heading and label copy on the samples
page so "app", "preferences", and "token" labels all use the same style.
@aws-amplify-us-east-2

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-738.d1b38q61t1z947.amplifyapp.com

{loginType === 'token' && (
<div>
<span>Your access token: </span>
<span>Your Access Token: </span>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You Access Token is:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants