in /documentation
/API-linting-Implementation-Guideline.md

line 40 and 42 should have relative links per the release

documentation
/Linting-rules.md

• line 35: the info-contact field is not supported in CAMARA OASs so line 35 should say "No"
• line 159: should be updated to say "may include "wip", "x.y.z-alpha.n" or "x.y;z-rc;n" while the API is not yer publicly released."

these changes can be done later as needed. Up to the team.

documentation
/UE-Identification.md

this file is very 3GPP focussed. it could be more logically placed in supporting documents (and even more logically in ICM ...) Not sure if there is a reference to it somewhere.
Also UE being a Telco term, it could be renamed to 3gpp-device-identification.md (where ever you put it.

Also inside the file terminology could be aligned (API invoker -> API consumer, UE -> device, etc), depending on the objective of this document.

Decision up to the team.

documentation
/Userstory-template.md

line 26 - is this reference still valid (e.g. it refers to API families), or should it point to the latest version of the CAMARA presentation (in the marketing or governance repo) or should there be an update created ?

btw, this same file is also in the local supporting documents folder, so maybe the link should point there ? (and updates would be there as well).

There are 2 open PRs labeled with Spring25 - should these go into the release 2.2 or later ?

There are 2 open PRs labeled with Spring25 - should these go into the release 2.2 or later ?

Yes labeled, but not planned in the r2.2
#277 - under final review - planned to be added for final release as it adds recommendations (considerations), no guidelines impacting API definitions
#317 - still draft can be replaced by the proposal of new guidelines document addressing #306

documentation /Linting-rules.md
/documentation /API-linting-Implementation-Guideline.md

Issue #394

documentation /Userstory-template.md

Issue #396

documentation /UE-Identification.md

Issue #397

Hi all, please check some comments for clarifications and a few alignment point from the Release Mgmt team. please check an handle as appropriate. after that RM can approve and /LGTM

Thank you @tanjadegroot for thorough review.
I have opened a bunch of issues to be resolved by Commonalites - mainly related to documentation files, to be resolved before public release