Update status of optee-os and optee-client in Debian/Apertis

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

content/concepts/op-tee.md

@@ -380,8 +380,8 @@ considered critical by project developers.
 ### OP-TEE OS
 
 The OP-TEE project provides the [OP-TEE OS](https://github.com/OP-TEE/optee_os)
-as the trusted OS that runs in the TEE.  This is not currently packaged for
-Debian and it would need to be to incorporated into Apertis.  Like ATF, an
+as the trusted OS that runs in the TEE.  `optee-os` is packaged for [Debian](https://tracker.debian.org/pkg/optee-os)
+and [Apertis](https://gitlab.apertis.org/pkg/optee-os).  Like ATF, an
 Apertis key will need to be used to sign the binaries intended for the TEE to
 ensure the chain of trust.  Currently when OP-TEE is built, it embeds the
 public key that will be used for verifying TAs.  As with the key/keys used in
@@ -408,8 +408,8 @@ In addition to the trusted OS, the OP-TEE project provides the
 [OP-TEE supplicant and TEE Client API](https://github.com/OP-TEE/optee_client).
 The supplicant provides services to OP-TEE that it does not directly provide
 itself and the TEE Client API provides a user space API in the REE to
-communicate with the TEE.  As with the OP-TEE OS, these components are
-currently not packaged for Debian and would need to be.  As these components
+communicate with the TEE.  `optee-client` is packaged for [Debian](https://tracker.debian.org/pkg/optee-client)
+and [Apertis](https://gitlab.apertis.org/pkg/optee-client).  As these components
 run in the REE they don't need to be signed.
 
 ### Sample TAs