[3.1-RC1] Editorial cleanup: clarity-only naming/description suggestions (7.6)

[henrylyons]

Affected Sections: model/Core/Properties/unitQUDT.md, processRationale.md; model/Hardware/Classes/HardwareProductSpecification.md; model/Operations/Properties/

Feedback
Clarity-only naming and description suggestions.

Suggested Change:

Section	Suggestion
model/Core/Properties/unitQUDT.md	Consider renaming unitQUDT to unit (uncommon acronym)
model/Core/Properties/processRationale.md	Add context describing when the property should be used
model/Hardware/Classes/HardwareProductSpecification.md	Document the hazard property and other properties
model/Operations/Properties/assessedElement.md, assessmentContext.md	Provide a Description that adds detail beyond the Summary

Notes:
This feedback was provided by Microsoft at the SPDX working group meeting on June 30, 2026.

[goneall]

Any renaming would be breaking - we should decide on any name changes before the 3.1 release.

Descriptions, on the other hand, can be done in the 3.1 release or later.

[bact]

/Core/unitQUDT is only introduced in 3.1-RC1, so it is possible to be renamed, if need to.

[goneall]

Discussed unitQUDT on 25 Aug 2026:

• The current name makes it clear the expected format
• Possible suggestion - we could add a datatype, so it would clearer what the format of the string is
  • General consensus that having a datatype without an additional restriction would increase the complexity, but not have much additional value

The remaining description updates are not breaking and can be done after 3.1 if needed.