fix reference to scrapi

draft-ietf-scitt-architecture.md

@@ -80,6 +80,8 @@ normative:
   CWT_CLAIM_COSE:
     target: https://datatracker.ietf.org/doc/draft-ietf-cose-cwt-claims-in-headers/
     title: CBOR Web Token (CWT) Claims in COSE Headers
+  I-D.draft-birkholz-scitt-scrapi: scrapi
+
 informative:
   I-D.draft-steele-cose-merkle-tree-proofs: COMETRE
   PBFT: DOI.10.1145/571637.571640
@@ -444,7 +446,7 @@ While the `Reg_Info` header MUST be present in all Signed Statements, all attrib
 The role of Transparency Service can be decomposed into several major functions.
 The most important is maintaining an Append-only Log, the verifiable data structure that records Signed Statements, and enforcing a Registration Policy.
 It also maintains a service key, which is used to endorse the state of the Append-only Log in Receipts.
-All Transparency Services MUST expose standard endpoints for Registration of Signed Statements and Receipt issuance, which is described in {{sec-messages}}.
+All Transparency Services MUST expose standard endpoints for Registration of Signed Statements and Receipt issuance, which is described in {{-scrapi}}.
 Each Transparency Service also defines its own Registration Policies, which MUST apply to all entries in the Append-only Log.
 
 The combination of Identity, Registration Policy evaluation, and the Transparency Service endpoint constitute the trusted part of the Transparency Service.