Brand compliance: trademark marks and HC3 product name corrections by ddemlow · Pull Request #31 · ScaleComputing/RestAPIExamples

ddemlow · 2026-06-13T18:55:59Z

Summary

README.md: Apply brand guidelines — add ™ to Scale Computing™, SC//HyperCore™, SC//Fleet™; add ® to Ansible® and Terraform® on first use; add trademark attribution footer
vm-lifecycle.ps1, specific_task/iso-upload.ps1, specific_task/SetTag.ps1: Update credential prompt text from obsolete "HC3" to "HyperCore"

What was skipped and why

specific_task/superaudit/test_database.py:104 — 'model': 'HC3' is a test fixture simulating the Node model field returned by the HyperCore API. Physical HC3 appliances return "HC3" (or e.g. "HC3-2300") as their hardware model string; changing it would make the test fixture factually incorrect.

Not in this PR

GitHub repo About/description field change (REST API Examples for SC//HyperCore™ and SC//Fleet™ platform manager) — needs to be set via GitHub Settings → About.

🤖 Generated with Claude Code

- README.md: add ™/® marks to Scale Computing, SC//HyperCore, SC//Fleet, Ansible, and Terraform per brand guidelines; add trademark attribution footer - vm-lifecycle.ps1, iso-upload.ps1, SetTag.ps1: update credential prompt from obsolete "HC3" to "HyperCore" Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

- README.md: "specific Scale release" → "specific Scale Computing release" - specific_task/README.md: "against a Scale system" / "on a scale system" → "SC//HyperCore™ cluster" - platform_2025/README.md: add ™ to title to match root README - Platform2025_SnapshotExampleBash.sh: fix "Scale Compuintg" typo and expand to "Scale Computing HyperCore" Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

metchason

Looks pretty good, left a few nit-picky comments

metchason · 2026-07-28T17:06:47Z

    [ValidateNotNullOrEmpty()]
    [string] $Server,
-    [PSCredential] $Credential = (Get-Credential -Message "Enter Scale HC3 Credentials"),
+    [PSCredential] $Credential = (Get-Credential -Message "Enter SC//HyperCore Credentials"),


Enter SC//HyperCore virtualization suite credentials

metchason · 2026-07-28T17:07:02Z

-These scripts are only examples and demonstrate common use cases with the API.  
-Refer to the API docs on a scale system for a detailed guide on available calls.
+These scripts are only examples and demonstrate common use cases with the API.
+Refer to the API docs on a SC//HyperCore™ cluster for a detailed guide on available calls.


SC//HyperCore™ virtualization suite cluster

metchason · 2026-07-28T17:07:18Z

 	[Parameter(mandatory=$true)]
 	[string]$setTag,
-	[PSCredential] $Cred = (Get-Credential -Message "Enter Scale HC3 Credentials")
+	[PSCredential] $Cred = (Get-Credential -Message "Enter SC//HyperCore Credentials")


"Enter SC//HyperCore virtualization suite credentials"

metchason · 2026-07-28T17:08:06Z

@@ -1,10 +1,10 @@
-# Scale Computing Platform REST API Examples
+# Scale Computing™ Platform REST API Examples


We are retiring the SC//Platform umbrella (other than the conference name). I would say "Scale Computing™ REST API Examples"

metchason · 2026-07-28T17:09:26Z

+# Scale Computing™ Platform REST API Examples

-This repository contains several example scripts for running API queries against a HyperCore cluster or Fleet Manager.
+This repository contains several example scripts for running API queries against an **SC//HyperCore™** cluster or **SC//Fleet™** platform manager.


SC//HyperCore™ virtualization suite cluster or SC//Fleet Manager™ edge orchestration software

metchason · 2026-07-28T17:10:15Z

+These scripts are only examples and demonstrate common use cases with the APIs.

-Refer to this repository's tags for examples tied to a specific Scale release.
+Refer to this repository's tags for examples tied to a specific Scale Computing release.


Scale Computing™

metchason · 2026-07-28T17:10:39Z

+
+---
+
+SC//HyperCore™ and SC//Fleet™ are trademarks of Scale Computing, Inc.


SC//Fleet Manager™

Per review on PR #31: - Drop retired "SC//Platform" umbrella from README titles - Use full product names: SC//HyperCore virtualization suite, SC//Fleet Manager edge orchestration software - Add ™ to "specific Scale Computing™ release" - Expand credential prompt text to "Enter SC//HyperCore virtualization suite credentials" Conference name "SC//Platform" retained in platform_2025/README.md per reviewer's carve-out. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

ddemlow · 2026-07-29T19:07:02Z

Thanks for the review — all 7 comments addressed in abf124e.

File	Change
`README.md:1`	Dropped the retired "Platform" umbrella → `Scale Computing™ REST API Examples`
`README.md:3`	`SC//HyperCore™ virtualization suite cluster or SC//Fleet Manager™ edge orchestration software`
`README.md:7`	`specific Scale Computing™ release`
`README.md:25`	Trademark footer: `SC//Fleet™` → `SC//Fleet Manager™`
`specific_task/README.md:3,6`	`SC//HyperCore™ virtualization suite cluster`
`specific_task/iso-upload.ps1:22`	`Enter SC//HyperCore virtualization suite credentials`
`specific_task/SetTag.ps1:26`	Same credential prompt text

Two consistency edits beyond the literal comments — both files were already in this PR's diff and each carried a string flagged elsewhere:

vm-lifecycle.ps1:26 — the third instance of the identical credential prompt
platform_2025/README.md:1 — same Scale Computing™ Platform title

Deliberately left alone: platform_2025/README.md:3 still reads "during the SC//Platform 'Maximizing Hypercore Rest API' session", per your carve-out for the conference name.

One open question for you: specific_task/README.md:1 reads "Scale Computing System REST API Examples". Not something you flagged and I haven't touched it, but "System" looks like similar stale umbrella wording — happy to align it to Scale Computing™ REST API Examples - Task Specific if you agree.

taylor-leick

one comment, otherwise looks good

taylor-leick · 2026-07-29T20:22:20Z

@@ -1,9 +1,9 @@
 # Scale Computing System REST API Examples - Task Specific


probably should make the same edit as below "SC//HyperCore™ Cluster REST API Examples - Task Specific"

Updated the title to reflect the correct branding of SC//HyperCore™.

ddemlow and others added 3 commits June 13, 2026 14:55

Use SC//HyperCore in credential prompt text

10e9b48

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

ddemlow requested a review from taylor-leick June 14, 2026 11:07

ddemlow self-assigned this Jul 27, 2026

ddemlow requested review from Sauce123, metchason and mjlyon July 27, 2026 17:21

metchason reviewed Jul 28, 2026

View reviewed changes

taylor-leick approved these changes Jul 29, 2026

View reviewed changes

Update README title to SC//HyperCore™ Cluster

e45553c

Updated the title to reflect the correct branding of SC//HyperCore™.

ddemlow merged commit c604d76 into master Jul 30, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Brand compliance: trademark marks and HC3 product name corrections - #31

Brand compliance: trademark marks and HC3 product name corrections#31
ddemlow merged 5 commits into
masterfrom
brand/trademark-compliance

ddemlow commented Jun 13, 2026

Uh oh!

metchason left a comment

Uh oh!

metchason Jul 28, 2026

Uh oh!

metchason Jul 28, 2026

Uh oh!

metchason Jul 28, 2026

Uh oh!

metchason Jul 28, 2026

Uh oh!

metchason Jul 28, 2026

Uh oh!

metchason Jul 28, 2026

Uh oh!

metchason Jul 28, 2026

Uh oh!

ddemlow commented Jul 29, 2026

Uh oh!

taylor-leick left a comment

Uh oh!

taylor-leick Jul 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

		@@ -1,10 +1,10 @@
		# Scale Computing Platform REST API Examples
		# Scale Computing™ Platform REST API Examples


		---

		SC//HyperCore™ and SC//Fleet™ are trademarks of Scale Computing, Inc.

		@@ -1,9 +1,9 @@
		# Scale Computing System REST API Examples - Task Specific

Uh oh!

Conversation

ddemlow commented Jun 13, 2026

Summary

What was skipped and why

Not in this PR

Uh oh!

metchason left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ddemlow commented Jul 29, 2026

Uh oh!

taylor-leick left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants