@hannestschofenig why do we need to define this term in the TEEP architecture? The term is used nowhere in the document after the terminology section. It's used once on line 153 of the markdown, but is used in a way that i think is clear in context without needing a definition.

The term "software update" only appears once in the TEEP architecture draft, and it is in the introduction before the terminology section:

To simplify the life of TA developers interacting with TAs in a TEE, an interoperable protocol for managing TAs running in different TEEs of various devices is needed. This software update protocol needs to make sure that compatible trusted and untrusted components (if any) of an application are installed on the correct device. In this TEE ecosystem, there often arises a need for an external trusted party to verify the identity, claims, and rights of TA developers, devices, and their TEEs. This trusted third party is the Trusted Application Manager (TAM).

Rather than trying to define it formally in a terminology section, I'd rather either remove the use of the term "software update" or make sure it's clear in context. My personal opinion is that the latter is already the case.

Is this PR in response to some specific feedback? No Issue number is referenced.

The term sounds a common word to me. Do we have to define it?