Update amazon-bedrock.md - sync models description updated

Author: oenerayca

content/en/docs/appstore/use-content/platform-supported-content/modules/aws/amazon-bedrock.md

@@ -602,21 +602,21 @@ Currently, there are operations available to sync metadata about:
 The syncing process works the same for all of these operations. 
 
 1. The information about models / knowledge bases / agents is persistent in the mendix app's database on the initial sync.
-2. An association to the `AmazonBedrockRegion` object, that represents the AWS region used when syncing, is stored.
+2. An association to the `AmazonBedrockRegion` object, that represents the AWS region used when syncing, is stored (this is only the case for knowledge bases and agents). 
 3. On a subsequent syncing process the available data is extended and updated. No data will be removed from the app's database - even if it is no longer available on AWS. The reason is that existing usages of the object in the running application should not be removed.
 
 The available operations are described in the following sections. 
 
 #### Sync Models {#sync-models}
 
 The `Sync Models` activity allows you to retrieve and store metadata about available models on Amazon Bedrock in your app's database. 
-The model information is persistent in the `AmazonBedrockModel` entity.
+The model information is persistent in the `BedrockDeployedModel` entity.
 
-Information about the models output and input modalities are stored as associations to the `ModelModality` entity. 
+Information about the model's input modalities are stored as associations to the `InputModality` entity and its output modality is stored to the `OutputModality` attribute.
 The input modality describes which form of data can be sent to the model.
 The output modality describes which form of data the model will return. 
 
-Information about the models inference type is stored as association to the `ModelInferenceType` entity.
+Information about the model's inference type is stored as association to the `ModelInferenceType` entity.
 The inference type describes how the model can be accessed. *ON Demand* models are accessible by default and charged by usage. 
 
 The input and output for this service are shown in the table below: