update docs

Author: jotruon

website/docs/d/core_cpe_device_shape.html.markdown

@@ -10,7 +10,15 @@ description: |-
 # Data Source: oci_core_cpe_device_shape
 This data source provides details about a specific Cpe Device Shape resource in Oracle Cloud Infrastructure Core service.
 
-get single cpeDeviceShape object and list of the questions need to asked for that single cpeDeviceShape.
+Gets the detailed information about the specified CPE device type. This might include a set of questions
+that are specific to the particular CPE device type. The customer must supply answers to those questions
+(see [UpdateTunnelCpeDeviceConfig](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/TunnelCpeDeviceConfig/UpdateTunnelCpeDeviceConfig)).
+The service merges the answers with a template of other information for the CPE device type. The following
+operations return the merged content:
+
+  * [GetCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Cpe/GetCpeDeviceConfigContent)
+  * [GetIpsecCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/IPSecConnection/GetIpsecCpeDeviceConfigContent)
+  * [GetTunnelCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/TunnelCpeDeviceConfig/GetTunnelCpeDeviceConfigContent)
 
 
 ## Example Usage
@@ -26,20 +34,23 @@ data "oci_core_cpe_device_shape" "test_cpe_device_shape" {
 
 The following arguments are supported:
 
-* `cpe_device_shape_id` - (Required) The OCID of the CPE device shape.
+* `cpe_device_shape_id` - (Required) The [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the CPE device shape.
 
 
 ## Attributes Reference
 
 The following attributes are exported:
 
-* `cpe_device_info` - customer premise equipment hardware information
-	* `platform_software_version` - The CPE's vendor/platform version
-	* `vendor` - The CPE's hardware information
-* `cpe_device_shape_id` - The CPE device type's unique identifier.
-* `parameters` - list of questions to ask to cusomter regarding their cpe device in order to generate their cpe device config
-	* `display_name` - 
-	* `explanation` - 
-	* `key` - 
-* `template` - the template that will be combined together with customer input to render customer cpe device configuration
+* `cpe_device_info` - Basic information about this particular CPE device type.
+	* `platform_software_version` - The platform or software version of the CPE device.
+	* `vendor` - The vendor that makes the CPE device.
+* `cpe_device_shape_id` - The [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the CPE device shape. This value uniquely identifies the type of CPE device. 
+* `parameters` - For certain CPE devices types, the customer can provide answers to questions that are specific to the device type. This attribute contains a list of those questions. The Networking service merges the answers with other information and renders a set of CPE configuration content. To provide the answers, use [UpdateTunnelCpeDeviceConfig](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/TunnelCpeDeviceConfig/UpdateTunnelCpeDeviceConfig). 
+	* `display_name` - A descriptive label for the question (for example, to display in a form in a graphical interface). 
+	* `explanation` - A description or explanation of the question, to help the customer answer accurately. 
+	* `key` - A string that identifies the question. 
+* `template` - A template of CPE device configuration information that will be merged with the customer's answers to the questions to render the final CPE device configuration content. Also see:
+	* [GetCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Cpe/GetCpeDeviceConfigContent)
+	* [GetIpsecCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/IPSecConnection/GetIpsecCpeDeviceConfigContent)
+	* [GetTunnelCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/TunnelCpeDeviceConfig/GetTunnelCpeDeviceConfigContent) 
 

website/docs/d/core_cpe_device_shapes.html.markdown

@@ -10,7 +10,19 @@ description: |-
 # Data Source: oci_core_cpe_device_shapes
 This data source provides the list of Cpe Device Shapes in Oracle Cloud Infrastructure Core service.
 
-Lists the customer-premises equipment objects (CPEs)'s hardware information in the specified compartment.
+Lists the CPE device types that the Networking service provides CPE configuration
+content for (example: Cisco ASA). The content helps a network engineer configure
+the actual CPE device represented by a [Cpe](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Cpe/) object.
+
+If you want to generate CPE configuration content for one of the returned CPE device types,
+ensure that the [Cpe](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Cpe/) object's `cpeDeviceShapeId` attribute is set
+to the CPE device type's OCID (returned by this operation).
+
+For information about generating CPE configuration content, see these operations:
+
+  * [GetCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Cpe/GetCpeDeviceConfigContent)
+  * [GetIpsecCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/IPSecConnection/GetIpsecCpeDeviceConfigContent)
+  * [GetTunnelCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/TunnelCpeDeviceConfig/GetTunnelCpeDeviceConfigContent)
 
 
 ## Example Usage
@@ -36,13 +48,16 @@ The following attributes are exported:
 
 The following attributes are exported:
 
-* `cpe_device_info` - customer premise equipment hardware information
-	* `platform_software_version` - The CPE's vendor/platform version
-	* `vendor` - The CPE's hardware information
-* `cpe_device_shape_id` - The CPE device type's unique identifier.
-* `parameters` - list of questions to ask to cusomter regarding their cpe device in order to generate their cpe device config
-	* `display_name` - 
-	* `explanation` - 
-	* `key` - 
-* `template` - the template that will be combined together with customer input to render customer cpe device configuration
+* `cpe_device_info` - Basic information about this particular CPE device type.
+	* `platform_software_version` - The platform or software version of the CPE device.
+	* `vendor` - The vendor that makes the CPE device.
+* `cpe_device_shape_id` - The [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the CPE device shape. This value uniquely identifies the type of CPE device. 
+* `parameters` - For certain CPE devices types, the customer can provide answers to questions that are specific to the device type. This attribute contains a list of those questions. The Networking service merges the answers with other information and renders a set of CPE configuration content. To provide the answers, use [UpdateTunnelCpeDeviceConfig](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/TunnelCpeDeviceConfig/UpdateTunnelCpeDeviceConfig). 
+	* `display_name` - A descriptive label for the question (for example, to display in a form in a graphical interface). 
+	* `explanation` - A description or explanation of the question, to help the customer answer accurately. 
+	* `key` - A string that identifies the question. 
+* `template` - A template of CPE device configuration information that will be merged with the customer's answers to the questions to render the final CPE device configuration content. Also see:
+	* [GetCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Cpe/GetCpeDeviceConfigContent)
+	* [GetIpsecCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/IPSecConnection/GetIpsecCpeDeviceConfigContent)
+	* [GetTunnelCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/TunnelCpeDeviceConfig/GetTunnelCpeDeviceConfigContent) 
 

website/docs/d/core_cpes.html.markdown

@@ -40,7 +40,13 @@ The following attributes are exported:
 The following attributes are exported:
 
 * `compartment_id` - The OCID of the compartment containing the CPE.
-* `cpe_device_shape_id` - The CPE device type's unique identifier.
+* `cpe_device_shape_id` - The [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the CPE's device type. The Networking service maintains a general list of CPE device types (for example, Cisco ASA). For each type, Oracle provides CPE configuration content that can help a network engineer configure the CPE. The OCID uniquely identifies the type of device. To get the OCIDs for the device types on the list, see [ListCpeDeviceShapes](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/CpeDeviceShapeSummary/ListCpeDeviceShapes).
+
+	For information about how to generate CPE configuration content for a CPE device type, see:
+	* [GetCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Cpe/GetCpeDeviceConfigContent)
+	* [GetIpsecCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/IPSecConnection/GetIpsecCpeDeviceConfigContent)
+	* [GetTunnelCpeDeviceConfigContent](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/TunnelCpeDeviceConfig/GetTunnelCpeDeviceConfigContent)
+	* [GetTunnelCpeDeviceConfig](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/TunnelCpeDeviceConfig/GetTunnelCpeDeviceConfig) 
 * `defined_tags` - Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm).  Example: `{"Operations.CostCenter": "42"}` 
 * `display_name` - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information. 
 * `freeform_tags` - Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm).  Example: `{"Department": "Finance"}` 

website/docs/d/core_instance_credentials.html.markdown

@@ -10,8 +10,8 @@ description: |-
 # Data Source: oci_core_instance_credentials
 This data source provides details about a specific Instance Credential resource in Oracle Cloud Infrastructure Core service.
 
-Gets the generated credentials for the instance. Only works for instances that require password to log in (E.g. Windows).
-For certain OS'es, users will be forced to change the initial credentials.
+Gets the generated credentials for the instance. Only works for instances that require a password to log in, such as Windows.
+For certain operating systems, users will be forced to change the initial credentials.
 
 
 ## Example Usage

website/docs/d/core_network_security_group_security_rules.html.markdown

@@ -47,7 +47,7 @@ The following attributes are exported:
 * `destination` - Conceptually, this is the range of IP addresses that a packet originating from the instance can go to.
 
 	Allowed values:
-	* An IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56` Note that IPv6 addressing is currently supported only in the Government Cloud.
+	* An IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56` Note that IPv6 addressing is currently supported only in certain regions. See [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).
 	* The `cidrBlock` value for a [Service](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Service/), if you're setting up a security rule for traffic destined for a particular `Service` through a service gateway. For example: `oci-phx-objectstorage`.
 	* The OCID of a [NetworkSecurityGroup](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/NetworkSecurityGroup/) in the same VCN. The value can be the NSG that the rule belongs to if the rule's intent is to control traffic between VNICs in the same NSG. 
 * `destination_type` - Type of destination for the rule. Required if `direction` = `EGRESS`.
@@ -70,7 +70,7 @@ The following attributes are exported:
 * `source` - Conceptually, this is the range of IP addresses that a packet coming into the instance can come from.
 
 	Allowed values:
-	* An IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56` Note that IPv6 addressing is currently supported only in the Government Cloud.
+	* An IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56` Note that IPv6 addressing is currently supported only in certain regions. See [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).
 	* The `cidrBlock` value for a [Service](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Service/), if you're setting up a security rule for traffic coming from a particular `Service` through a service gateway. For example: `oci-phx-objectstorage`.
 	* The OCID of a [NetworkSecurityGroup](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/NetworkSecurityGroup/) in the same VCN. The value can be the NSG that the rule belongs to if the rule's intent is to control traffic between VNICs in the same NSG. 
 * `source_type` - Type of source for the rule. Required if `direction` = `INGRESS`.

website/docs/d/core_route_tables.html.markdown

@@ -66,7 +66,7 @@ The following attributes are exported:
 	* `destination` - Conceptually, this is the range of IP addresses used for matching when routing traffic. Required if you provide a `destinationType`.
 
 		Allowed values:
-		* IP address range in CIDR notation. Can be an IPv4 or IPv6 CIDR. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56`. If you set this to an IPv6 CIDR, the route rule's target can only be a DRG or internet gateway. Note that IPv6 addressing is currently supported only in the Government Cloud.
+		* IP address range in CIDR notation. Can be an IPv4 or IPv6 CIDR. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56`. If you set this to an IPv6 CIDR, the route rule's target can only be a DRG or internet gateway. Note that IPv6 addressing is currently supported only in certain regions. See [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).
 		* The `cidrBlock` value for a [Service](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Service/), if you're setting up a route rule for traffic destined for a particular `Service` through a service gateway. For example: `oci-phx-objectstorage`. 
 	* `destination_type` - Type of destination for the rule. Required if you provide a `destination`.
 		* `CIDR_BLOCK`: If the rule's `destination` is an IP address range in CIDR notation.

website/docs/d/core_security_lists.html.markdown

@@ -55,7 +55,7 @@ The following attributes are exported:
 	* `destination` - Conceptually, this is the range of IP addresses that a packet originating from the instance can go to.
 
 		Allowed values:
-		* IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56` Note that IPv6 addressing is currently supported only in the Government Cloud.
+		* IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56` Note that IPv6 addressing is currently supported only in certain regions. See [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).
 		* The `cidrBlock` value for a [Service](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Service/), if you're setting up a security list rule for traffic destined for a particular `Service` through a service gateway. For example: `oci-phx-objectstorage`. 
 	* `destination_type` - Type of destination for the rule. The default is `CIDR_BLOCK`.
 
@@ -100,7 +100,7 @@ The following attributes are exported:
 	* `source` - Conceptually, this is the range of IP addresses that a packet coming into the instance can come from.
 
 		Allowed values:
-		* IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56`. Note that IPv6 addressing is currently supported only in the Government Cloud.
+		* IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56`. Note that IPv6 addressing is currently supported only in certain regions. See [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).
 		* The `cidrBlock` value for a [Service](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Service/), if you're setting up a security list rule for traffic coming from a particular `Service` through a service gateway. For example: `oci-phx-objectstorage`. 
 	* `source_type` - Type of source for the rule. The default is `CIDR_BLOCK`.
 		* `CIDR_BLOCK`: If the rule's `source` is an IP address range in CIDR notation.

website/docs/d/core_subnet.html.markdown

@@ -47,7 +47,7 @@ The following attributes are exported:
 	Example: `subnet123` 
 * `freeform_tags` - Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm).  Example: `{"Department": "Finance"}` 
 * `id` - The subnet's Oracle ID (OCID).
-* `ipv6cidr_block` - For an IPv6-enabled subnet, this is the IPv6 CIDR block for the subnet's private IP address space. The subnet size is always /64. Note that IPv6 addressing is currently supported only in the Government Cloud.  Example: `2001:0db8:0123:1111::/64` 
+* `ipv6cidr_block` - For an IPv6-enabled subnet, this is the IPv6 CIDR block for the subnet's private IP address space. The subnet size is always /64. Note that IPv6 addressing is currently supported only in certain regions. See [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).  Example: `2001:0db8:0123:1111::/64` 
 * `ipv6public_cidr_block` - For an IPv6-enabled subnet, this is the IPv6 CIDR block for the subnet's public IP address space. The subnet size is always /64. The left 48 bits are inherited from the `ipv6PublicCidrBlock` of the [Vcn](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/Vcn/), and the remaining 16 bits are from the subnet's `ipv6CidrBlock`.  Example: `2001:0db8:0123:1111::/64` 
 * `ipv6virtual_router_ip` - For an IPv6-enabled subnet, this is the IPv6 address of the virtual router.  Example: `2001:0db8:0123:1111:89ab:cdef:1234:5678` 
 * `prohibit_public_ip_on_vnic` - Whether VNICs within this subnet can have public IP addresses. Defaults to false, which means VNICs created in this subnet will automatically be assigned public IP addresses unless specified otherwise during instance launch or VNIC creation (with the `assignPublicIp` flag in [CreateVnicDetails](https://docs.cloud.oracle.com/iaas/api/#/en/iaas/20160918/CreateVnicDetails/)). If `prohibitPublicIpOnVnic` is set to true, VNICs created in this subnet cannot have public IP addresses (that is, it's a private subnet).  Example: `true`