From 95b76173d5fc6d4047eea03ab62e200afe5f67f2 Mon Sep 17 00:00:00 2001
From: Riley Karson <rileykarson@google.com>
Date: Thu, 23 Jul 2020 10:31:29 -0700
Subject: [PATCH] Fix description for attribute import_custom_routes (#3777)

Co-authored-by: Muhammad Hamza Zaib <hamzazaib3202@gmail.com>
---
 .../website/docs/r/compute_network_peering.html.markdown        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/third_party/terraform/website/docs/r/compute_network_peering.html.markdown b/third_party/terraform/website/docs/r/compute_network_peering.html.markdown
index 9c90599d4afa..1f015838ac52 100644
--- a/third_party/terraform/website/docs/r/compute_network_peering.html.markdown
+++ b/third_party/terraform/website/docs/r/compute_network_peering.html.markdown
@@ -60,7 +60,7 @@ may belong to a different project.
 Whether to export the custom routes to the peer network. Defaults to `false`.
 
 * `import_custom_routes` - (Optional)
-Whether to export the custom routes from the peer network. Defaults to `false`.
+Whether to import the custom routes from the peer network. Defaults to `false`.
 
 * `export_subnet_routes_with_public_ip` - (Optional)
 Whether subnet routes with public IP range are exported. The default value is true, all subnet routes are exported. The IPv4 special-use ranges (https://en.wikipedia.org/wiki/IPv4#Special_addresses) are always exported to peers and are not controlled by this field.