Update Segura DSM DM - v3 (#5469)

Fixed product naming convention.

Signed-off-by: chellin-segura <chellin@segura.security>
Co-authored-by: Gergely Brautigam <skarlso777@gmail.com>

docs/provider/senhasegura-dsm.md

@@ -1,16 +1,15 @@
-## senhasegura DevOps Secrets Management (DSM)
+## Segura® DevOps Secret Manager (DSM)
 
-External Secrets Operator integrates with [senhasegura](https://senhasegura.com/) [DevOps Secrets Management (DSM)](https://senhasegura.com/devops) module to sync application secrets to secrets held on the Kubernetes cluster.
+External Secrets Operator integrates with [Segura®](https://segura.security/) [DevOps Secret Manager (DSM)](https://segura.security/solutions/devops) module to sync application secrets to secrets held on the Kubernetes cluster.
 
 ---
 
 ## Authentication
 
-Authentication in senhasegura uses DevOps Secrets Management (DSM) application authorization schema
+Authentication in Segura® uses DevOps Secret Manager (DSM) application authorization schema. Instructions to setup Authorizations and Secrets in Segura® DSM can be found at [Segura docs for DSM](https://docs.senhasegura.io/docs/how-to-manage-authorizations-per-application-in-devops-secret-manager).
 
-You need to create an Kubernetes Secret with desired auth parameters, for example:
+You will need to create an Kubernetes Secret with desired auth parameters, for example:
 
-Instructions to setup authorizations and secrets in senhasegura DSM can be found at [senhasegura docs for DSM](https://helpcenter.senhasegura.io/docs/3.22/dsm) and [senhasegura YouTube channel](https://www.youtube.com/channel/UCpDms35l3tcrfb8kZSpeNYw/search?query=DSM%2C%20en-US)
 
 ```yaml
 {% include 'senhasegura-dsm-secret.yaml' %}
@@ -20,7 +19,7 @@ Instructions to setup authorizations and secrets in senhasegura DSM can be found
 
 ## Examples
 
-To sync secrets between senhasegura and Kubernetes with External Secrets, we need to define an SecretStore or ClusterSecretStore resource with senhasegura provider, setting authentication in DSM module with Secret defined before
+To sync secrets between Segura® DSM and Kubernetes with External Secrets, you need to define a SecretStore or ClusterSecretStore resource with Segura® provider, setting up authentication in the DSM module with the Secret you defined before.
 
 ### SecretStore
 
@@ -38,7 +37,7 @@ To sync secrets between senhasegura and Kubernetes with External Secrets, we nee
 
 ## Syncing secrets
 
-In examples below, consider that three secrets (api-settings, db-settings and hsm-settings) are defined in senhasegura DSM
+In examples below, consider that three secrets (api-settings, db-settings and hsm-settings) are defined in Segura® DSM
 
 ---
 
@@ -80,7 +79,7 @@ HSM_PORT='9223'
 
 ### Sync DSM secrets using Secret Identifiers
 
-You can fetch all key/value pairs for a given secret identifier If you leave the remoteRef.property empty. This returns the json-encoded secret value for that path.
+You can fetch all key/value pairs for a given secret identifier if you leave the remoteRef.property empty. This returns the json-encoded secret value for that path.
 
 If you only need a specific key, you can select it using remoteRef.property as the key name.
 
@@ -101,15 +100,15 @@ API_SETTINGS_TOKEN='example-token-value'
 
 ### Sync DSM secrets using Secret Identifiers with automatically name assignments
 
-If your app requires multiples secrets, it is not required to create multiple ExternalSecret resources, you can aggregate secrets using a single ExternalSecret resource
+If your app requires multiples secrets, it is not required to create multiple ExternalSecret resources, as you can aggregate secrets using a single ExternalSecret resource.
 
-In this method, every secret data in senhasegura creates an Kubernetes Secret `.data.X` field
+In this method, every secret data in Segura® creates a Kubernetes Secret `.data.X` field
 
 ``` yaml
 {% include 'senhasegura-dsm-external-secret-multiple.yaml' %}
 ```
 
-Kubernetes Secret will be create with follow `.data.X`
+Kubernetes Secret will be created with the following `.data.X`
 
 ```bash
 URL='https://example.com/api/example'
@@ -130,7 +129,7 @@ You can sync all secrets that your authorization in DSM has using find, in a fut
 {% include 'senhasegura-dsm-external-secret-all.yaml' %}
 ```
 
-Kubernetes Secret will be create with follow `.data.X`
+Kubernetes Secret will be created with the following `.data.X`
 
 ```bash
 URL='https://example.com/api/example'