Fix description for attribute import_custom_routes (#3777) (#2301)

Co-authored-by: Muhammad Hamza Zaib <[email protected]>
Signed-off-by: Modular Magician <[email protected]>

Co-authored-by: Muhammad Hamza Zaib <[email protected]>

Author: modular-magician

.changelog/3777.txt

@@ -0,0 +1,3 @@
+```release-note:none
+
+```

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.