Fix sentences after removal of USE_PSA
Some sentences or paragraphs became confusing or meaningless after
removing USE_PSA and only fixing the local context/semantics.
Fix the semantics where needed and remove parts that became meaningless.
Signed-off-by: Janos Follath <janos.follath@arm.com>
diff --git a/README.md b/README.md
index 7d3a435..b00d21a 100644
--- a/README.md
+++ b/README.md
@@ -295,8 +295,6 @@
Mbed TLS includes a reference implementation of the PSA Cryptography API.
However, it does not aim to implement the whole specification; in particular it does not implement all the algorithms.
-The X.509 and TLS code can use PSA cryptography for most operations. See `docs/use-psa-crypto.md` for details.
-
### PSA drivers
Mbed TLS supports drivers for cryptographic accelerators, secure elements and random generators. This is work in progress. Please note that the driver interfaces are not fully stable yet and may change without notice. We intend to preserve backward compatibility for application code (using the PSA Crypto API), but the code of the drivers may have to change in future minor releases of Mbed TLS.
diff --git a/docs/architecture/psa-migration/strategy.md b/docs/architecture/psa-migration/strategy.md
index f7f7ff6..6acdf34 100644
--- a/docs/architecture/psa-migration/strategy.md
+++ b/docs/architecture/psa-migration/strategy.md
@@ -28,8 +28,8 @@
We currently have a few compile-time options that are relevant to the migration:
-- `MBEDTLS_PSA_CRYPTO_C` - enabled by default, controls the presence of the PSA
- Crypto APIs.
+- `MBEDTLS_PSA_CRYPTO_C` - enabled by default, controls the presence of the
+ implementation of PSA Crypto APIs.
- `PSA_CRYPTO_CONFIG` - disabled by default, supports builds with drivers and
without the corresponding software implementation (G5 above).