diff --git a/website/docs/r/google_kms_crypto_key_iam_binding.html.markdown b/website/docs/r/google_kms_crypto_key_iam_binding.html.markdown
index 0479e785..16b592b9 100644
--- a/website/docs/r/google_kms_crypto_key_iam_binding.html.markdown
+++ b/website/docs/r/google_kms_crypto_key_iam_binding.html.markdown
@@ -14,7 +14,7 @@ an existing Google Cloud KMS crypto key.
 ## Example Usage
 
 ```hcl
-resource "google_kms_crypto_key_binding" "crypto_key" {
+resource "google_kms_crypto_key_iam_binding" "crypto_key" {
   crypto_key_id = "your-crypto-key-id"
   role          = "roles/editor"
 
@@ -51,5 +51,5 @@ exported:
 IAM binding imports use space-delimited identifiers; first the resource in question and then the role.  These bindings can be imported using the `crypto_key_id` and role, e.g.
 
 ```
-$ terraform import google_kms_crypto_key_binding.my_binding "your-project-id/location-name/key-name roles/viewer"
+$ terraform import google_kms_crypto_key_iam_binding.my_binding "your-project-id/location-name/key-name roles/viewer"
 ```