doc: Corrected StackGres camel case

Author: Cepxio

doc/content/en/04-administration-guide/01-stackgres-installation/03-installation-via-operatorhub/_index.md

@@ -111,7 +111,7 @@ Remember to remove the generated password hint from the secret to avoid security
     kubectl patch secret --namespace stackgres stackgres-restapi-admin --type json -p '[{"op":"remove","path":"/data/clearPassword"}]'
 ```
 
-Modify the configuration by patching the stackgres SGConfig
+Modify the configuration by patching the StackGres SGConfig
 
 ```
 cat << EOF | kubectl patch -n openshift-operators sgconfig stackgres --type merge -p "$(cat)"
@@ -173,7 +173,7 @@ To watch the operator installation you may look at Pods in the `openshift-operat
 kubectl get pod -n openshift-operators --watch
 ```
 
-Modify the configuration by patching the stackgres SGConfig:
+Modify the configuration by patching the StackGres SGConfig:
 
 ```
 cat << EOF | kubectl patch -n openshift-operators sgconfig stackgres --type merge -p "$(cat)"

doc/content/en/04-administration-guide/02-connecting-to-the-cluster/01-passwords/_index.md

@@ -10,15 +10,15 @@ showToc: true
 When creating a cluster, StackGres randomly generates passwords, for the `postgres` superuser and others.
 The passwords are stored in a secret (named as the cluster).
 
-By default, a Stackgres cluster initialization creates 3 users:
+By default, a StackGres cluster initialization creates 3 users:
 
 - `superuser`
 - `replication`
 - `authenticator`
 
 The passwords are stored in that secret under the keys `<user>-password`.
 
-Assuming that we have a Stackgres cluster named `cluster`, we can get the passwords with the following commands:
+Assuming that we have a StackGres cluster named `cluster`, we can get the passwords with the following commands:
 
 - **superuser / postgres:**
 

doc/content/en/04-administration-guide/05-backups/04-oke/_index.md

@@ -23,13 +23,13 @@ Create the required permissions and the user with following characteristics (tha
 Create the `stackgres-demo-k8s-user` user:
 
 ```
-oci iam user create --name stackgres-demo-k8s-user --description 'Stackgres backup user'
+oci iam user create --name stackgres-demo-k8s-user --description 'StackGres backup user'
 ```
 
 Create the group that the user will be a part of, which will have access to the bucket:
 
 ```
-oci iam group create --name stackgres-backup-group --description 'Stackgres backup group'
+oci iam group create --name stackgres-backup-group --description 'StackGres backup group'
 ```
 
 Add the user to the group:
@@ -61,7 +61,7 @@ Create a policy to allow the created group to use the bucket:
   oci iam policy create \
   --compartment-id $s3compartment_id \
   --name stackfres-backup-policy \
-  --description 'Policy to use the bucket for Stackgres backups' \
+  --description 'Policy to use the bucket for StackGres backups' \
   --statements '["Allow group stackgres-backup-group to use bucket on compartment id '$s3compartment_id' where target.bucket.name = '/''backup-demo-of-stackgres-io'/''"]'
 ```
 

doc/content/en/04-administration-guide/10-replication/03-remote-cluster/_index.md

@@ -6,7 +6,7 @@ description: This section explains how to setup external replication for a clust
 showToc: true
 ---
 
-Having a Postgres server replica outside the main 'DC|Zone|Geografic Area' is the next level of High Avaliability. DBA teams already know stories of companies losing the entire DC because of different physical issues and even more, when working with k8s and having many cloud providers a door is open to the options of setting up Stackgres across k8s platform services and migrating from one to other without any vendor restriction. Therefore, Stackgres already added the support to create external cluster replicas.
+Having a Postgres server replica outside the main 'DC|Zone|Geografic Area' is the next level of High Avaliability. DBA teams already know stories of companies losing the entire DC because of different physical issues and even more, when working with k8s and having many cloud providers a door is open to the options of setting up StackGres across k8s platform services and migrating from one to other without any vendor restriction. Therefore, StackGres already added the support to create external cluster replicas.
 
 Lets do it!
 

doc/content/en/04-administration-guide/10-replication/_index.md

@@ -6,6 +6,6 @@ aliases: [ /tutorial/admin/replication ]
 description: This page contains details about how to create different cluster arquitecture topologies by using the replication features.
 ---
 
-Stackgres supports all Postgres and Patroni features to set the different replication options that come with these technologies. Indeed, Stackgres don't use any custom owned replication mechanism or protocol, it fully relies upon the official Postgres replication development. Furthermore, Stackgres relies upon the Patroni HA development, therefore, failOver, switchOver, and replication should work as any other Postgres cluster.
+StackGres supports all Postgres and Patroni features to set the different replication options that come with these technologies. Indeed, StackGres don't use any custom owned replication mechanism or protocol, it fully relies upon the official Postgres replication development. Furthermore, StackGres relies upon the Patroni HA development, therefore, failOver, switchOver, and replication should work as any other Postgres cluster.
 
 {{% children style="li" depth="1" description="true" %}}

doc/content/en/04-administration-guide/14-sharded-cluster/13-connecting-to-the-sharded-cluster/01-passwords/_index.md

@@ -9,15 +9,15 @@ showToc: true
 When creating a sharded cluster, StackGres randomly generates passwords, for the `postgres` superuser and others.
 The passwords are stored in a secret (named as the sharded cluster).
 
-By default, a Stackgres sharded cluster initialization creates 3 users:
+By default, a StackGres sharded cluster initialization creates 3 users:
 
 - `superuser`
 - `replication`
 - `authenticator`
 
 The passwords are stored in that secret under the keys `<user>-password`.
 
-Assuming that we have a Stackgres sharded cluster named `cluster`, we can get the passwords with the following commands:
+Assuming that we have a StackGres sharded cluster named `cluster`, we can get the passwords with the following commands:
 
 - **superuser / postgres:**
 

doc/content/en/07-developer-documentation/06-contributing-guide/_index.md

@@ -12,7 +12,7 @@ Please observe the following rules when contributing to StackGres:
 
 * [Create an issue](https://gitlab.com/ongresinc/stackgres/issues/new) with any question or improvements about the source code, to keep the discussion organized.
 
-* Contact us at stackgres at ongres dot com before sending a merge request, to have a contributor agreement signed with us.
+* Contact us at StackGres at Ongres dot com before sending a merge request, to have a contributor agreement signed with us.
   This is a requirement for your merge request to be merged upstream.
 
 * Changes and merge requests should be performed from the `development` branch, instead of `main`.

doc/content/en/faq.md

@@ -16,7 +16,7 @@ StackGres source code is licensed under the [OSI](https://opensource.org/license
 
 ## Is there a “GPL-free” commercial license for StackGres?
 
-Yes. Contact us at stackgres at ongres doc com if you want a trial or commercial license that does not contain the GPL clauses.
+Yes. Contact us at StackGres at Ongres doc com if you want a trial or commercial license that does not contain the GPL clauses.
 
 ## Will you ever switch from an open-source license to a source-available one?