From fc1b5ee67ab008c160b35f33c4fa144ed4cc902c Mon Sep 17 00:00:00 2001
From: "Eldor Pulatov [EPAM/GCP]" <eldor_pulatov@epam.com>
Date: Thu, 3 Nov 2022 12:21:17 +0000
Subject: [PATCH] GONRG-5890-Change-to-GC

---
 .gitlab/merge_request_templates/default.md | 2 +-
 README.md                                  | 4 ++--
 provider/search-gcp/README.md              | 8 ++++----
 provider/search-gcp/docs/anthos/README.md  | 2 +-
 provider/search-gcp/docs/gcp/README.md     | 4 ++--
 5 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/.gitlab/merge_request_templates/default.md b/.gitlab/merge_request_templates/default.md
index 30b572826..9dc78d756 100644
--- a/.gitlab/merge_request_templates/default.md
+++ b/.gitlab/merge_request_templates/default.md
@@ -10,7 +10,7 @@
 ## Does this introduce a change in the cloud provider implementation, if so which cloud?
 - [ ] AWS 
 - [ ] Azure
-- [ ] GCP
+- [ ] Google Cloud
 - [ ] IBM
 
 ## Does this introduce a breaking change?
diff --git a/README.md b/README.md
index e32946220..4ae65b0ac 100644
--- a/README.md
+++ b/README.md
@@ -17,9 +17,9 @@ limitations under the License.
 
 All documentation for the Azure implementation of `os-search` lives [here](./provider/search-azure/README.md)
 
-## GCP Implementation
+## Google Cloud Implementation
 
-All documentation for the GCP implementation of `os-search` lives [here](./provider/search-gcp/README.md)
+All documentation for the GC implementation of `os-search` lives [here](./provider/search-gcp/README.md)
 
 ## AWS Implementation
 
diff --git a/provider/search-gcp/README.md b/provider/search-gcp/README.md
index 097d3a808..80a1f519b 100644
--- a/provider/search-gcp/README.md
+++ b/provider/search-gcp/README.md
@@ -17,8 +17,8 @@ Pre-requisites
 ## Service Configuration
 ### Anthos:
 [Anthos service configuration ](docs/anthos/README.md)
-### GCP:
-[Gcp service configuration ](docs/gcp/README.md)
+### Google Cloud:
+[Google Cloud service configuration ](docs/gcp/README.md)
 
 ### Run Locally
 Check that maven is installed:
@@ -112,8 +112,8 @@ This section describes how to run cloud OSDU E2E tests.
 
 ### Anthos test configuration:
 [Anthos service configuration ](docs/anthos/README.md)
-### GCP test configuration:
-[Gcp service configuration ](docs/gcp/README.md)
+### Google Cloud test configuration:
+[Google Cloud service configuration ](docs/gcp/README.md)
 
 ## Deployment
 
diff --git a/provider/search-gcp/docs/anthos/README.md b/provider/search-gcp/docs/anthos/README.md
index 2ca54f35f..a82a76936 100644
--- a/provider/search-gcp/docs/anthos/README.md
+++ b/provider/search-gcp/docs/anthos/README.md
@@ -8,7 +8,7 @@ Must have:
 
 | name | value | description | sensitive? | source |
 | ---  | ---   | ---         | ---        | ---    |
-| `SPRING_PROFILES_ACTIVE` | ex `anthos` | Spring profile that activate default configuration for GCP environment | false | - |
+| `SPRING_PROFILES_ACTIVE` | ex `anthos` | Spring profile that activate default configuration for Google Cloud environment | false | - |
 | `<ELASTICSEARCH_USER_ENV_VARIABLE_NAME>` | ex `user` | Elasticsearch user, name of that variable not defined at the service level, the name will be received through partition service. Each tenant can have it's own ENV name value, and it must be present in ENV of Indexer service, see [Partition properties set](#Properties-set-in-Partition-service)  | yes | - |
 | `<ELASTICSEARCH_PASSWORD_ENV_VARIABLE_NAME>` | ex `password` | Elasticsearch password, name of that variable not defined at the service level, the name will be received through partition service. Each tenant can have it's own ENV name value, and it must be present in ENV of Indexer service, see [Partition properties set](#Properties-set-in-Partition-service) | false | - |
 
diff --git a/provider/search-gcp/docs/gcp/README.md b/provider/search-gcp/docs/gcp/README.md
index c0320e08d..8a2b108b8 100644
--- a/provider/search-gcp/docs/gcp/README.md
+++ b/provider/search-gcp/docs/gcp/README.md
@@ -1,4 +1,4 @@
-## Service Configuration for GCP
+## Service Configuration for Google Cloud
 
 ## Environment variables:
 
@@ -8,7 +8,7 @@ Must have:
 
 | name | value | description | sensitive? | source |
 | ---  | ---   | ---         | ---        | ---    |
-| `SPRING_PROFILES_ACTIVE` | ex `gcp` | Spring profile that activate default configuration for GCP environment | false | - |
+| `SPRING_PROFILES_ACTIVE` | ex `gcp` | Spring profile that activate default configuration for Google Cloud environment | false | - |
 | `GOOGLE_AUDIENCES` | ex `*****.apps.googleusercontent.com` | Client ID for getting access to cloud resources | yes | https://console.cloud.google.com/apis/credentials |
 | `<ELASTICSEARCH_USER_ENV_VARIABLE_NAME>` | ex `user` | Elasticsearch user, name of that variable not defined at the service level, the name will be received through partition service. Each tenant can have it's own ENV name value, and it must be present in ENV of Indexer service, see [Partition properties set](#Properties-set-in-Partition-service)  | yes | - |
 | `<ELASTICSEARCH_PASSWORD_ENV_VARIABLE_NAME>` | ex `password` | Elasticsearch password, name of that variable not defined at the service level, the name will be received through partition service. Each tenant can have it's own ENV name value, and it must be present in ENV of Indexer service, see [Partition properties set](#Properties-set-in-Partition-service) | false | - |
-- 
GitLab