Rename Lightwheel

[mingxueg-nv]

Fixes #ISSUE_NUMBER

Rename LightWheel to Lightwheel

[greptile-apps]

Greptile Summary

This PR performs a brand name correction — "LightWheel" → "Lightwheel" (lowercase 'w') — in the README display text and a single inline comment in assets.py. The actual S3 URL path segments (Props/LightWheel/…) are intentionally left unchanged, so no asset loading is affected by this diff.

Confidence Score: 5/5

Safe to merge — only documentation text and a code comment were changed; no functional code was altered.

Both changed lines are purely cosmetic (README prose and a Python comment). The S3 URL paths that drive actual asset loading remain untouched, so there is no runtime risk introduced by this PR. No P0/P1 findings remain.

No files require special attention.

Important Files Changed

Filename	Overview
workflows/rheo/README.md	Single-word rename of "LightWheel" → "Lightwheel" in the SimReady Assets section; purely cosmetic documentation change.
workflows/rheo/scripts/simulation/assets/assets.py	Only the inline comment "# Props Powered by LightWheel" was updated to "Lightwheel"; all S3 URL path segments (Props/LightWheel/…) remain unchanged, keeping the actual asset URLs intact.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: Rename LightWheel → Lightwheel] --> B[README.md]
    A --> C[assets.py]
    B --> D["Display text updated\n'LightWheel' → 'Lightwheel'"]
    C --> E["Comment updated\n'# Props Powered by LightWheel'\n→ '# Props Powered by Lightwheel'"]
    C --> F["S3 URL paths unchanged\nProps/LightWheel/... retained"]
    F --> G["Assets still resolve\nto existing S3 objects"]

Loading

_{Reviews (2): Last reviewed commit: "Revert S3 assets path" | Re-trigger Greptile}

[greptile-apps]

S3 path case-sensitivity may break asset loading

AWS S3 object keys are case-sensitive. Renaming the URL path segment from Props/LightWheel/ to Props/Lightwheel/ will return HTTP 403/404 for every asset unless the objects in the omniverse-content-production S3 bucket have already been moved or re-keyed to match the new casing. Please confirm the S3-side paths have been updated before merging, or these asset URLs will silently fail at runtime.