Skip to content

Refine README content for clarity and conciseness - #263

Closed
FujitsuPolycom wants to merge 1 commit into
mainfrom
FujitsuPolycom-patch-2
Closed

Refine README content for clarity and conciseness#263
FujitsuPolycom wants to merge 1 commit into
mainfrom
FujitsuPolycom-patch-2

Conversation

@FujitsuPolycom

Copy link
Copy Markdown
Owner

Removed redundant information about token capacity and clarified the status of switched deployments.

What and why

Validation

Additional context

  • I removed credentials and private site identifiers from the change.
  • I identified copied or adapted work and updated third-party notices when required.

Removed redundant information about token capacity and clarified the status of switched deployments.
@FujitsuPolycom

Copy link
Copy Markdown
Owner Author

Closing as superseded. This PR was authored against pre-#262 main; a re-diff against current main shows it would remove the R33 release documentation added by #262 and #261 — the Generic R33 image profile rows, the bounded-qualified status paragraphs, the 7.5 GiB / 1,081,922-token KV record, and the R33 container-image table entry — and restore the pre-R33 table (8.75 GiB prose, shared-image rows, 'implemented/research-only' status) that #262 deliberately replaced.

The valid intent here — trimming redundant KV-capacity prose and clarifying switched-deployment status — is already satisfied on current main: the qualification-status paragraphs are the present-state record the repository requires, and the switched-deployment caveat survives in the current text. A fresh pass against today's README is welcome if more trimming is wanted.

@FujitsuPolycom
FujitsuPolycom deleted the FujitsuPolycom-patch-2 branch September 11, 2026 20:09
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.

1 participant