[Tracking] Minor UI Polish Follow-ups

[SeaCelo]

Now that the v5.5 work has landed, this issue is a running place to collect minor UI polish items and small presentation cleanups.

This is for things like:

• button labels
• wording and spelling
• small layout polish
• minor visual cleanup
• small discoverability improvements

If you have an idea for a change, please add it in the comments here before opening a PR. It would be better to collect a few small polish items together where possible instead of submitting too many tiny PRs.

This is not for larger behavior changes or anything that would undermine upstream compatibility. If something starts to change logic or move the app away from upstream behavior in a meaningful way, it should go into its own issue instead.

[Vishal27alpha]

I’ve identified and fixed several UI text issues in AddCase.js and DataFile.js (spelling and minor grammar fixes). Submitted PR #374 addressing these items.

[lil-aditya]

Hi @SeaCelo few things I noticed that seem like a good fit for this tracking issue:

• Fix the typoed button class btn tn-white btn-default in the Pivot “Save” action and several scenario action buttons , looks like btn had a small identity crisis there 😅 and it can cause inconsistent rendering.

• Remove the stray > showing up in the Data File and Model File page subtitles.

• In the Pivot “Create view” modal, change ...not allowed in model name → ...not allowed in view name (like different meaning is coming).

All of these are small changes mostly wording and minor UI cleanup.

[MahadevBalla]

One small thing I had noticed: when I select something like Shadow price - UDC Equality (which has no data), it shows the error message, but the Pivot still shows the previous selection’s data.

Not sure if this is intended or just a small UI/state thing. Should this go under this tracking issue, or better to raise it as a separate bug?

[brightyorcerf]

I've performed a global audit of the v5.5 branding and UI surface to identify remaining inconsistencies. I can bundle the following into a single Identity & Branding PR to keep the noise low:

1. Branding & Identity Alignment

• Global Rename: Transition all user-facing labels from 'MUIO' to 'MUIOGO' across Navbar, Home, Settings, and the DataFile diagnostics pages.
• Timeline Update: Advance the footer and metadata copyright from 2025 to 2026 in index.html.
• Asset Restoration: Fix the commented-out favicon path in index.html and link it to the branded MUIOGO asset.

2. Wording & Typography Fixes

• Typo Correction: Fix Deleteing → Deleting and Plese → Please in the DataFile controller alerts.
• CSS Class Cleanup: Resolve a bulk typo where btn tn-white was used instead of btn-white across ~15 parameter views (RYSeDt, RYC, Pivot, etc.), and remove duplicate btn classes in Html.Class.js.
• Standardization: Align loader messages (e.g., 'Generating log file...') to follow the ... ellipsis convention used elsewhere in the app.

3. Visual & Navigation Polish

• Stray Characters: Fix the stray > characters appearing in the subtitles of ModelFile.html and DataFile.html (escaped to >).
• Discoverability: Add 'Back' or 'Home' navigation controls to the new ModelFile and DataFile pages to improve the user flow.

4. UX & Navigation Refinements

• Equation Readability: Add horizontal scroll containers for MathJax equations in ModelFile.html to prevent layout breaking on smaller viewports.
• Splash Screen Alignment: Ensure the initial loading overlay in index.html reflects the MUIOGO branding.
• Casing Consistency: Standardize page headers (e.g., 'Model file' → 'Model File') for a more cohesive UI.