Fix collapsed markdown for enum values on Terraform website

.changelog/3783.txt

@@ -0,0 +1,3 @@
+```release-note:bug
+Fix markdown for enum values
+```

website/docs/r/access_context_manager_access_level.html.markdown

@@ -94,12 +94,14 @@ The following arguments are supported:
 
 * `basic` -
   (Optional)
-  A set of predefined conditions for the access level and a combining function.  Structure is documented below.
+  A set of predefined conditions for the access level and a combining function.
+  Structure is documented below.
 
 * `custom` -
   (Optional)
   Custom access level conditions are set using the Cloud Common Expression Language to represent the necessary conditions for the level to apply to a request. 
-  See CEL spec at: https://github.com/google/cel-spec.  Structure is documented below.
+  See CEL spec at: https://github.com/google/cel-spec.
+  Structure is documented below.
 
 
 The `basic` block supports:
@@ -111,16 +113,13 @@ The `basic` block supports:
   conditions must be satisfied for the AccessLevel to be applied. If
   OR is used, at least one Condition in conditions must be satisfied
   for the AccessLevel to be applied.
-
-  Default value: `AND`
-
-  Possible values are:
-  * `AND`
-  * `OR`
+  Default value is `AND`.
+  Possible values are `AND` and `OR`.
 
 * `conditions` -
   (Required)
-  A set of requirements for the AccessLevel to be granted.  Structure is documented below.
+  A set of requirements for the AccessLevel to be granted.
+  Structure is documented below.
 
 
 The `conditions` block supports:
@@ -166,7 +165,8 @@ The `conditions` block supports:
   (Optional)
   Device specific restrictions, all restrictions must hold for
   the Condition to be true. If not specified, all devices are
-  allowed.  Structure is documented below.
+  allowed.
+  Structure is documented below.
 
 * `regions` -
   (Optional)
@@ -195,7 +195,8 @@ The `device_policy` block supports:
 * `os_constraints` -
   (Optional)
   A list of allowed OS versions.
-  An empty list allows all types and all versions.  Structure is documented below.
+  An empty list allows all types and all versions.
+  Structure is documented below.
 
 * `require_admin_approval` -
   (Optional)
@@ -217,21 +218,16 @@ The `os_constraints` block supports:
 * `os_type` -
   (Required)
   The operating system type of the device.
-
-  Possible values are:
-  * `OS_UNSPECIFIED`
-  * `DESKTOP_MAC`
-  * `DESKTOP_WINDOWS`
-  * `DESKTOP_LINUX`
-  * `DESKTOP_CHROME_OS`
+  Possible values are `OS_UNSPECIFIED`, `DESKTOP_MAC`, `DESKTOP_WINDOWS`, `DESKTOP_LINUX`, and `DESKTOP_CHROME_OS`.
 
 The `custom` block supports:
 
 * `expr` -
   (Required)
   Represents a textual expression in the Common Expression Language (CEL) syntax. CEL is a C-like expression language.
   This page details the objects and attributes that are used to the build the CEL expressions for 
-  custom access levels - https://cloud.google.com/access-context-manager/docs/custom-access-level-spec.  Structure is documented below.
+  custom access levels - https://cloud.google.com/access-context-manager/docs/custom-access-level-spec.
+  Structure is documented below.
 
 
 The `expr` block supports:

website/docs/r/access_context_manager_service_perimeter.html.markdown

@@ -154,25 +154,23 @@ The following arguments are supported:
   topologies with many independent perimeters that need to share some data
   with a common perimeter, but should not be able to share data among
   themselves.
-
-  Default value: `PERIMETER_TYPE_REGULAR`
-
-  Possible values are:
-  * `PERIMETER_TYPE_REGULAR`
-  * `PERIMETER_TYPE_BRIDGE`
+  Default value is `PERIMETER_TYPE_REGULAR`.
+  Possible values are `PERIMETER_TYPE_REGULAR` and `PERIMETER_TYPE_BRIDGE`.
 
 * `status` -
   (Optional)
   ServicePerimeter configuration. Specifies sets of resources,
   restricted services and access levels that determine
-  perimeter content and boundaries.  Structure is documented below.
+  perimeter content and boundaries.
+  Structure is documented below.
 
 * `spec` -
   (Optional)
   Proposed (or dry run) ServicePerimeter configuration.
   This configuration allows to specify and test ServicePerimeter configuration
   without enforcing actual access restrictions. Only allowed to be set when
-  the `useExplicitDryRunSpec` flag is set.  Structure is documented below.
+  the `useExplicitDryRunSpec` flag is set.
+  Structure is documented below.
 
 * `use_explicit_dry_run_spec` -
   (Optional)
@@ -218,7 +216,8 @@ The `status` block supports:
 * `vpc_accessible_services` -
   (Optional)
   Specifies how APIs are allowed to communicate within the Service
-  Perimeter.  Structure is documented below.
+  Perimeter.
+  Structure is documented below.
 
 
 The `vpc_accessible_services` block supports:
@@ -264,7 +263,8 @@ The `spec` block supports:
 * `vpc_accessible_services` -
   (Optional)
   Specifies how APIs are allowed to communicate within the Service
-  Perimeter.  Structure is documented below.
+  Perimeter.
+  Structure is documented below.
 
 
 The `vpc_accessible_services` block supports:

website/docs/r/app_engine_application_url_dispatch_rules.html.markdown

@@ -92,7 +92,8 @@ The following arguments are supported:
 
 * `dispatch_rules` -
   (Required)
-  Rules to match an HTTP request and dispatch that request to a service.  Structure is documented below.
+  Rules to match an HTTP request and dispatch that request to a service.
+  Structure is documented below.
 
 
 The `dispatch_rules` block supports:

website/docs/r/app_engine_domain_mapping.html.markdown

@@ -64,18 +64,15 @@ The following arguments are supported:
 
 * `ssl_settings` -
   (Optional)
-  SSL configuration for this domain. If unconfigured, this domain will not serve with SSL.  Structure is documented below.
+  SSL configuration for this domain. If unconfigured, this domain will not serve with SSL.
+  Structure is documented below.
 
 * `override_strategy` -
   (Optional)
   Whether the domain creation should override any existing mappings for this domain.
   By default, overrides are rejected.
-
-  Default value: `STRICT`
-
-  Possible values are:
-  * `STRICT`
-  * `OVERRIDE`
+  Default value is `STRICT`.
+  Possible values are `STRICT` and `OVERRIDE`.
 
 * `project` - (Optional) The ID of the project in which the resource belongs.
     If it is not provided, the provider project is used.
@@ -96,10 +93,7 @@ The `ssl_settings` block supports:
   (Required)
   SSL management type for this domain. If `AUTOMATIC`, a managed certificate is automatically provisioned.
   If `MANUAL`, `certificateId` must be manually specified in order to configure SSL for this domain.
-
-  Possible values are:
-  * `AUTOMATIC`
-  * `MANUAL`
+  Possible values are `AUTOMATIC` and `MANUAL`.
 
 * `pending_managed_certificate_id` -
   ID of the managed `AuthorizedCertificate` resource currently being provisioned, if applicable. Until the new
@@ -119,7 +113,8 @@ In addition to the arguments listed above, the following computed attributes are
 
 * `resource_records` -
   The resource records required to configure this domain mapping. These records must be added to the domain's DNS
-  configuration in order to serve the application via this domain mapping.  Structure is documented below.
+  configuration in order to serve the application via this domain mapping.
+  Structure is documented below.
 
 
 The `resource_records` block contains:
@@ -135,11 +130,7 @@ The `resource_records` block contains:
 * `type` -
   (Optional)
   Resource record type. Example: `AAAA`.
-
-  Possible values are:
-  * `A`
-  * `AAAA`
-  * `CNAME`
+  Possible values are `A`, `AAAA`, and `CNAME`.
 
 ## Timeouts
 

website/docs/r/app_engine_firewall_rule.html.markdown

@@ -73,11 +73,7 @@ The following arguments are supported:
 * `action` -
   (Required)
   The action to take if this rule matches.
-
-  Possible values are:
-  * `UNSPECIFIED_ACTION`
-  * `ALLOW`
-  * `DENY`
+  Possible values are `UNSPECIFIED_ACTION`, `ALLOW`, and `DENY`.
 
 
 - - -