diff --git a/README.md b/README.md
index 25c2b5536..d2058e41b 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS prov
 
 ## What It Does
 
-Inspired by [Kubernetes DNS](https://github.com/kubernetes/dns), Kubernetes' cluster-internal DNS server, ExternalDNS makes Kubernetes resources discoverable via public DNS servers. Like KubeDNS, it retrieves a list of resources (Services, Ingresses, etc.) from the [Kubernetes API](https://kubernetes.io/docs/api/) to determine a desired list of DNS records. *Unlike* KubeDNS, however, it's not a DNS server itself, but merely configures other DNS providers accordingly—e.g. [AWS Route 53](https://aws.amazon.com/route53/) or [Google CloudDNS](https://cloud.google.com/dns/docs/).
+Inspired by [Kubernetes DNS](https://github.com/kubernetes/dns), Kubernetes' cluster-internal DNS server, ExternalDNS makes Kubernetes resources discoverable via public DNS servers. Like KubeDNS, it retrieves a list of resources (Services, Ingresses, etc.) from the [Kubernetes API](https://kubernetes.io/docs/api/) to determine a desired list of DNS records. *Unlike* KubeDNS, however, it's not a DNS server itself, but merely configures other DNS providers accordingly—e.g. [AWS Route 53](https://aws.amazon.com/route53/) or [Google Cloud DNS](https://cloud.google.com/dns/docs/).
 
 In a broader sense, ExternalDNS allows you to control DNS records dynamically via Kubernetes resources in a DNS provider-agnostic way.
 
@@ -24,7 +24,7 @@ To see ExternalDNS in action, have a look at this [video](https://www.youtube.co
 ## The Latest Release: v0.5
 
 ExternalDNS' current release is `v0.5`. This version allows you to keep selected zones (via `--domain-filter`) synchronized with Ingresses and Services of `type=LoadBalancer` in various cloud providers:
-* [Google CloudDNS](https://cloud.google.com/dns/docs/)
+* [Google Cloud DNS](https://cloud.google.com/dns/docs/)
 * [AWS Route 53](https://aws.amazon.com/route53/)
 * [AWS Service Discovery](https://docs.aws.amazon.com/Route53/latest/APIReference/overview-service-discovery.html)
 * [AzureDNS](https://azure.microsoft.com/en-us/services/dns)
diff --git a/docs/contributing/getting-started.md b/docs/contributing/getting-started.md
index 8ce2325c6..9fe764c37 100644
--- a/docs/contributing/getting-started.md
+++ b/docs/contributing/getting-started.md
@@ -14,7 +14,7 @@ This list of endpoints is passed to the [Plan](../../plan) which determines the
 
 Once the difference has been figured out the list of intended changes is passed to a `Registry` which live in the [registry](../../registry) package. The registry is a wrapper and access point to DNS provider. Registry implements the ownership concept by marking owned records and filtering out records not owned by ExternalDNS before passing them to DNS provider.
 
-The [provider](../../provider) is the adapter to the DNS provider, e.g. Google CloudDNS. It implements two methods: `ApplyChanges` to apply a set of changes filtered by `Registry` and `Records` to retrieve the current list of records from the DNS provider.
+The [provider](../../provider) is the adapter to the DNS provider, e.g. Google Cloud DNS. It implements two methods: `ApplyChanges` to apply a set of changes filtered by `Registry` and `Records` to retrieve the current list of records from the DNS provider.
 
 The orchestration between the different components is controlled by the [controller](../../controller).
 
diff --git a/docs/contributing/sources-and-providers.md b/docs/contributing/sources-and-providers.md
index e5d1cd995..3d51b3598 100644
--- a/docs/contributing/sources-and-providers.md
+++ b/docs/contributing/sources-and-providers.md
@@ -29,7 +29,7 @@ All sources live in package `source`.
 ### Providers
 
 Providers are an abstraction over any kind of sink for desired Endpoints, e.g.:
-* storing them in Google CloudDNS
+* storing them in Google Cloud DNS
 * printing them to stdout for testing purposes
 * fanning out to multiple nested providers
 
@@ -46,7 +46,7 @@ The interface tries to be generic and assumes a flat list of records for both fu
 
 All providers live in package `provider`.
 
-* `GoogleProvider`: returns and creates DNS records in Google CloudDNS
+* `GoogleProvider`: returns and creates DNS records in Google Cloud DNS
 * `AWSProvider`: returns and creates DNS records in AWS Route 53
 * `AzureProvider`: returns and creates DNS records in Azure DNS
 * `InMemoryProvider`: Keeps a list of records in local memory
diff --git a/docs/faq.md b/docs/faq.md
index 927a5b9a4..38b72aac3 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -30,7 +30,7 @@ ExternalDNS can solve this for you as well.
 
 Currently, the following providers are supported: 
 
-- Google CloudDNS
+- Google Cloud DNS
 - AWS Route 53
 - AzureDNS
 - CloudFlare