diff --git a/_docs_explore/42-transport-layer.md b/_docs_explore/42-transport-layer.md
index 627e973ae..317f70397 100644
--- a/_docs_explore/42-transport-layer.md
+++ b/_docs_explore/42-transport-layer.md
@@ -15,7 +15,7 @@ The transport layer is located between the Backbone layer and the consumption la
## Data Handling
-The transport layer introduces a local storage based on a document database. In this database all relevant data is persisted or cached. In addition to the database, the transport layer takes care of serializing and deserializing data structures.
+The transport layer introduces a local storage based on a document database. In this database all relevant data is persisted. In addition to the database, the transport layer takes care of serializing and deserializing data structures.
## Syntactical validation of plaintext data
diff --git a/_docs_integrate/data-model-overview.md b/_docs_integrate/data-model-overview.md
index 9c267f2b8..f4296553d 100644
--- a/_docs_integrate/data-model-overview.md
+++ b/_docs_integrate/data-model-overview.md
@@ -63,7 +63,7 @@ A Token has the following properties:
| forIdentity | `string` \| `undefined` | Can be set to an enmeshed address. If set, then only the [Identity]({% link _docs_integrate/data-model-overview.md %}#identity) with that `address` can retrieve the Token from the Backbone. |
| passwordProtection | [`PasswordProtection`](#passwordprotection) \| `undefined` | Information about whether or not the Token is protected by a password or pin. | |
| reference | [`ObjectReference`](#objectreference) | {% include descr_reference class="Token" %} | saved only locally |
-| isEphemeral | `boolean` | If set to `true` the Token will not be cached in the database and only displayed once. You will not be able to fetch this Token unless you remember its reference. |
+| isEphemeral | `boolean` | If set to `true` the Token will not be persisted in the database and only displayed once. You will not be able to fetch this Token unless you remember its reference. |
### PasswordProtection
diff --git a/_docs_integrate/error-codes.md b/_docs_integrate/error-codes.md
index ee7044c18..d6365a89b 100644
--- a/_docs_integrate/error-codes.md
+++ b/_docs_integrate/error-codes.md
@@ -119,7 +119,6 @@ Please find a list of enmeshed error codes below. Most often the errors occur on
| {% include anchor a="error.runtime.attributes.
noPreviousVersionOfRepositoryAttributeHasBeenSharedWithPeerBefore" %} | No previous version of the given [RepositoryAttribute]({% link _docs_integrate/data-model-overview.md %}#localattribute) has been shared with this peer before. If you wish to execute an initial sharing of this Attribute, [use 'ShareRepositoryAttribute']({% link _docs_integrate/share-attributes-with-peer.md %}). |
| {% include anchor a="error.runtime.attributes.setDefaultRepositoryAttributesIsDisabled" %} | Setting default RepositoryAttributes is disabled for this Account. |
| {% include anchor a="error.runtime.attributes.repositoryAttributeHasAlreadyBeenSharedWithPeer" %} | The given [RepositoryAttribute]({% link _docs_integrate/data-model-overview.md %}#localattribute) has already been shared with this peer. |
-| {% include anchor a="error.runtime.cacheEmpty" %} | The `cache` of a [File]({% link _docs_integrate/data-model-overview.md %}#file), an [IdentityDeletionProcess]({% link _docs_integrate/data-model-overview.md %}#identitydeletionprocess), a [Message]({% link _docs_integrate/data-model-overview.md %}#message), a [Relationship]({% link _docs_integrate/data-model-overview.md %}#relationship), a [RelationshipTemplate]({% link _docs_integrate/data-model-overview.md %}#relationshiptemplate) or a [Token]({% link _docs_integrate/data-model-overview.md %}#token) is empty. |
| {% include anchor a="error.runtime.challenges.invalidChallenge" %} | The `challengeString` is invalid. |
| {% include anchor a="error.runtime.challenges.invalidSignature" %} | The `signature` is invalid. |
| {% include anchor a="error.runtime.decide.requestConfigDoesNotMatchResponseConfig" %} | The automation configuration specified when using the [Decider Module]({% link _docs_explore/61-runtime.md %}#decider-module) is invalid because the `requestConfig` does not match the `responseConfig`. |
@@ -166,7 +165,6 @@ Please find a list of enmeshed error codes below. Most often the errors occur on
| {% include anchor a="error.transport.challenges.challengeTypeRequiresActiveRelationship" %} | The challengeType `"Relationship"` requires an active [Relationship]({% link _docs_integrate/data-model-overview.md %}#relationship). |
| {% include anchor a="error.transport.datawallet.currentBiggerThanTarget" %} | The current datawallet version is bigger than the target version. |
| {% include anchor a="error.transport.datawallet.insufficientSupportedDatawalletVersion" %} | The current SupportedDatawalletVersion is too low to perform the requested operation. This means that the datawallet of the [Identity]({% link _docs_integrate/data-model-overview.md %}#identity) was upgraded by another device with a higher version. It is necessary to update the current device. |
-| {% include anchor a="error.transport.datawallet.unsupportedModification" %} | The following collections were received in CacheChanged datawallet modifications but are not supported by the current version of this library. |
| {% include anchor a="error.transport.devices.alreadyOnboarded" %} | The device has already been onboarded. |
| {% include anchor a="error.transport.devices.couldNotDeleteDevice" %} | The device cannot be deleted as the device is already onboarded or the Backbone did not authorize the deletion. |
| {% include anchor a="error.transport.files.cipherMismatch" %} | The actual hash of the cipher does not match the given cipherHash. Something went wrong while storing/transmitting the file. |
diff --git a/_docs_use-cases/use-case-transport-check-if-relationship-can-be-created.md b/_docs_use-cases/use-case-transport-check-if-relationship-can-be-created.md
index e47715222..663e93626 100644
--- a/_docs_use-cases/use-case-transport-check-if-relationship-can-be-created.md
+++ b/_docs_use-cases/use-case-transport-check-if-relationship-can-be-created.md
@@ -57,7 +57,7 @@ If the [Request Module]({% link _docs_explore/61-runtime.md %}#request-module) i
- Returns a `result` that indicates if a [Relationship]({% link _docs_integrate/data-model-overview.md %}#relationship) can be created with the given parameters.
- If the `isSuccess` property of the `result` has the value `true`, a [Relationship]({% link _docs_integrate/data-model-overview.md %}#relationship) can currently be created to the creator of the RelationshipTemplate. This would then initially have `"Pending"` as `status` until the creator of the RelationshipTemplate [accepts the Relationship]({% link _docs_use-cases/use-case-transport-accept-relationship.md %}).
- If the `isSuccess` property of the `result` has the value `false`, no [Relationship]({% link _docs_integrate/data-model-overview.md %}#relationship) can currently be created to the creator of the RelationshipTemplate. This can have various causes, for example:
- - The `templateId` does not resolve to a [RelationshipTemplate]({% link _docs_integrate/data-model-overview.md %}#relationshiptemplate) or the associated RelationshipTemplate was not cached correctly.
+ - The `templateId` does not resolve to a [RelationshipTemplate]({% link _docs_integrate/data-model-overview.md %}#relationshiptemplate).
- The [RelationshipTemplate]({% link _docs_integrate/data-model-overview.md %}#relationshiptemplate) has already expired, which means that the timestamp specified in its `expiresAt` property has been exceeded.
- A [Relationship]({% link _docs_integrate/data-model-overview.md %}#relationship) with `"Pending"`, `"Active"`, `"Terminated"` or `"DeletionProposed"` as `status` already exists to the creator of the RelationshipTemplate. In particular, the initiation of a new Relationship is prevented if the potential initiator has already [decomposed the former Relationship]({% link _docs_integrate/terminate-relationships.md %}#decompose-a-relationship) to the RelationshipTemplate's creator, but the creator of the RelationshipTemplate has not yet decomposed it and still has the former Relationship with `"DeletionProposed"` as `status`.
- The [Identity]({% link _docs_integrate/data-model-overview.md %}#identity) of the creator of the RelationshipTemplate is in deletion or has already been deleted.
diff --git a/_docs_use-cases/use-case-transport-create-own-token.md b/_docs_use-cases/use-case-transport-create-own-token.md
index 0a5c47ce6..06a3074b0 100644
--- a/_docs_use-cases/use-case-transport-create-own-token.md
+++ b/_docs_use-cases/use-case-transport-create-own-token.md
@@ -48,7 +48,7 @@ Creates a [Token]({% link _docs_integrate/data-model-overview.md %}#token) that
- `content` an arbitrary JSON structure of the data to share via the Token.
- `expiresAt` is the ISODateTime the Token expires at.
-- `ephemeral` indicates if the Token should be ephemeral and thus not be stored and cached on the local database. This is especially useful for Tokens which are created regularly, e.g. for RelationshipTemplates and doesn't need to be stored.
+- `ephemeral` indicates if the Token should be ephemeral and thus not be stored in the local database. This is especially useful for Tokens which are created regularly, e.g. for RelationshipTemplates and doesn't need to be stored.
- `forIdentity` can be set to an enmeshed address. If set, only the [Identity]({% link _docs_integrate/data-model-overview.md %}#identity) with that `address` can load the Token from the Backbone.
- `passwordProtection` can be specified as an object for [PasswordProtection]({% link _docs_integrate/data-model-overview.md %}#passwordprotection) of a Token. If set, only the Identities that know the password specified within the `passwordProtection.password` property of the Token can load it from the Backbone. In addition, the optional property `passwordProtection.passwordIsPin` can be used to configure the UI of the App in case the password is a pin.
diff --git a/_docs_use-cases/use-case-transport-create-relationship-with-relationshiptemplate.md b/_docs_use-cases/use-case-transport-create-relationship-with-relationshiptemplate.md
index 3a25bbd98..ebd39cdb7 100644
--- a/_docs_use-cases/use-case-transport-create-relationship-with-relationshiptemplate.md
+++ b/_docs_use-cases/use-case-transport-create-relationship-with-relationshiptemplate.md
@@ -61,7 +61,7 @@ To check whether a Relationship can be created without actually creating it, the
## On Failure
-- The `templateId` does not resolve to a [RelationshipTemplate]({% link _docs_integrate/data-model-overview.md %}#relationshiptemplate) or the associated RelationshipTemplate was not cached correctly.
+- The `templateId` does not resolve to a [RelationshipTemplate]({% link _docs_integrate/data-model-overview.md %}#relationshiptemplate).
- The [RelationshipTemplate]({% link _docs_integrate/data-model-overview.md %}#relationshiptemplate) has already expired, which means that the timestamp specified in its `expiresAt` property has been exceeded.
- A [Relationship]({% link _docs_integrate/data-model-overview.md %}#relationship) with `"Pending"`, `"Active"`, `"Terminated"` or `"DeletionProposed"` as `status` already exists to the creator of the RelationshipTemplate. In particular, the initiation of a new Relationship is prevented if the potential initiator has already [decomposed the former Relationship]({% link _docs_integrate/terminate-relationships.md %}#decompose-a-relationship) to the RelationshipTemplate's creator, but the creator of the RelationshipTemplate has not yet decomposed it and still has the former Relationship with `"DeletionProposed"` as `status`.
- The [Identity]({% link _docs_integrate/data-model-overview.md %}#identity) of the creator of the RelationshipTemplate is in deletion or has already been deleted.
diff --git a/_docs_use-cases/use-case-transport-create-token-for-file.md b/_docs_use-cases/use-case-transport-create-token-for-file.md
index 8a572a41e..589cfcd08 100644
--- a/_docs_use-cases/use-case-transport-create-token-for-file.md
+++ b/_docs_use-cases/use-case-transport-create-token-for-file.md
@@ -48,7 +48,7 @@ Creates a [Token]({% link _docs_integrate/data-model-overview.md %}#token) for a
- `fileId` is the `id` of the File the Token should be created for.
- Optionally, `expiresAt` can be specified, which describes the ISODateTime the Token expires at.
-- Optionally, `ephemeral` can be specified, which indicates if the Token should be ephemeral and thus not be stored and cached on the local database. This is especially useful for Tokens which are created regularly, e.g. for [RelationshipTemplates]({% link _docs_integrate/data-model-overview.md %}#relationshiptemplate), and don't need to be stored.
+- Optionally, `ephemeral` can be specified, which indicates if the Token should be ephemeral and thus not be stored in the local database. This is especially useful for Tokens which are created regularly, e.g. for [RelationshipTemplates]({% link _docs_integrate/data-model-overview.md %}#relationshiptemplate), and don't need to be stored.
- Optionally, `forIdentity` can be specified, which names the `address` of the only [Identity]({% link _docs_integrate/data-model-overview.md %}#identity) that will be able to load the Token from the Backbone.
- Optionally, `passwordProtection` can be specified as an object for [PasswordProtection]({% link _docs_integrate/data-model-overview.md %}#passwordprotection) of a Token. If set, only the Identities that know the password specified within the `passwordProtection.password` property of the Token can load it from the Backbone. In addition, the optional property `passwordProtection.passwordIsPin` can be used to configure the UI of the App in case the password is a pin.
diff --git a/_docs_use-cases/use-case-transport-create-token-for-own-relationshiptemplate.md b/_docs_use-cases/use-case-transport-create-token-for-own-relationshiptemplate.md
index dbe3ecfc0..23f1e4d4d 100644
--- a/_docs_use-cases/use-case-transport-create-token-for-own-relationshiptemplate.md
+++ b/_docs_use-cases/use-case-transport-create-token-for-own-relationshiptemplate.md
@@ -50,7 +50,7 @@ Creates a [Token]({% link _docs_integrate/data-model-overview.md %}#token) for a
- `templateId` is the `id` of the RelationshipTemplate the Token should be created for.
- `expiresAt` is the ISODateTime the Token expires at.
-- `ephemeral` indicates if the Token should be ephemeral and thus not be stored and cached on the local database. This is especially useful for Tokens which are created regularly, e.g. for RelationshipTemplates and doesn't need to be stored.
+- `ephemeral` indicates if the Token should be ephemeral and thus not be stored in the local database. This is especially useful for Tokens which are created regularly, e.g. for RelationshipTemplates and doesn't need to be stored.
- `forIdentity` can be set to an enmeshed address. If set, only the [Identity]({% link _docs_integrate/data-model-overview.md %}#identity) with that `address` can load the Token from the Backbone. If the RelationshipTemplate is already personalized via its `forIdentity` property, the Token created from it must have the same personalization.
- `passwordProtection` can be specified as an object for [PasswordProtection]({% link _docs_integrate/data-model-overview.md %}#passwordprotection) of a Token. If set, only the Identities that know the password specified within the `passwordProtection.password` property of the Token can load it from the Backbone. In addition, the optional property `passwordProtection.passwordIsPin` can be used to configure the UI of the App in case the password is a pin. If the RelationshipTemplate is already password protected via its `passwordProtection` property, the Token created from it must have the same password protection.
diff --git a/_docs_use-cases/use-case-transport-download-file.md b/_docs_use-cases/use-case-transport-download-file.md
index da1d54bfa..dc820a5d5 100644
--- a/_docs_use-cases/use-case-transport-download-file.md
+++ b/_docs_use-cases/use-case-transport-download-file.md
@@ -43,7 +43,7 @@ api_route_regex: ^GET /api/v2/Files/{id}/Download$
{% include properties_list.html %}
This use case allows to download the [File's]({% link _docs_integrate/data-model-overview.md %}#file) binary content that corresponds to the `fileId`.
-As the File is not stored or cached within the Connector, the encrypted File is downloaded from the Backbone, decrypted and returned every time this use case is called.
+As the File is not stored within the Connector, the encrypted File is downloaded from the Backbone, decrypted and returned every time this use case is called.
An [uploaded own File]({% link _docs_use-cases/use-case-transport-upload-own-file.md %}) can be downloaded by this use case in any case.
However, a File from a peer must first be [loaded]({% link _docs_use-cases/use-case-transport-load-file.md %}) before its actual content can be downloaded.
diff --git a/_includes/descr_expiresAt b/_includes/descr_expiresAt
index a2ed7e64f..c13fb2012 100644
--- a/_includes/descr_expiresAt
+++ b/_includes/descr_expiresAt
@@ -1 +1 @@
-A timestamp that describes when the {{ include.class }} expires on the Backbone. An expired {{ include.class }} cannot be fetched from the Backbone anymore. However, the cached version of the {{ include.class }} on Connector and App will still be accessible.
\ No newline at end of file
+A timestamp that describes when the {{ include.class }} expires on the Backbone. An expired {{ include.class }} cannot be fetched from the Backbone anymore. However, the stored version of the {{ include.class }} on Connector and App will still be accessible.
\ No newline at end of file