oci-vnmonitoring 2.76.1 → 2.77.1

package/lib/model/cross-connect-mapping.d.ts

@@ -15,7 +15,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
 /**
 * For use with Oracle Cloud Infrastructure FastConnect. Each
 * {@link VirtualCircuit} runs on one or
-* more cross-connects or cross-connect groups. A `CrossConnectMapping`
+* more cross-connects or cross-connect groups. A {@code CrossConnectMapping}
 * contains the properties for an individual cross-connect or cross-connect group
 * associated with a given virtual circuit.
 * <p>
@@ -39,7 +39,7 @@ Who specifies the BGP peering information in the case of customer connection via
 * peering information. There's one exception: for a public virtual circuit, Oracle
 * specifies the BGP IPv4 addresses.
 * <p>
-Every `CrossConnectMapping` must have BGP IPv4 peering addresses. BGP IPv6 peering
+Every {@code CrossConnectMapping} must have BGP IPv4 peering addresses. BGP IPv6 peering
 * addresses are optional. If BGP IPv6 addresses are provided, the customer can
 * exchange IPv6 routes with Oracle.
 *
@@ -69,7 +69,7 @@ export interface CrossConnectMapping {
   * <p>
   There's one exception: for a public virtual circuit, Oracle specifies the BGP IPv4 addresses.
   * <p>
-  Example: `10.0.0.18/31`
+  Example: {@code 10.0.0.18/31}
   *
       */
     "customerBgpPeeringIp"?: string;
@@ -81,7 +81,7 @@ export interface CrossConnectMapping {
   * <p>
   There's one exception: for a public virtual circuit, Oracle specifies the BGP IPv4 addresses.
   * <p>
-  Example: `10.0.0.19/31`
+  Example: {@code 10.0.0.19/31}
   *
       */
     "oracleBgpPeeringIp"?: string;
@@ -97,7 +97,7 @@ export interface CrossConnectMapping {
   IPv6 addressing is supported for all commercial and government regions. See
   * [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).
   * <p>
-  Example: `2001:db8::1/64`
+  Example: {@code 2001:db8::1/64}
   *
       */
     "customerBgpPeeringIpv6"?: string;
@@ -112,7 +112,7 @@ export interface CrossConnectMapping {
   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).
   * <p>
-  Example: `2001:db8::2/64`
+  Example: {@code 2001:db8::2/64}
   *
       */
     "oracleBgpPeeringIpv6"?: string;
@@ -122,7 +122,7 @@ export interface CrossConnectMapping {
   * or cross-connect group (the customer if the customer is colocated with Oracle, or
   * the provider if the customer is connecting via provider).
   * <p>
-  Example: `200`
+  Example: {@code 200}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "vlan"?: number;

package/lib/model/cross-connect-port-speed-shape.d.ts

@@ -20,14 +20,14 @@ export interface CrossConnectPortSpeedShape {
     /**
       * The name of the port speed shape.
   * <p>
-  Example: `10 Gbps`
+  Example: {@code 10 Gbps}
   *
       */
     "name": string;
     /**
       * The port speed in Gbps.
   * <p>
-  Example: `10`
+  Example: {@code 10}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "portSpeedInGbps": number;

package/lib/model/cross-connect-status.d.ts

@@ -27,7 +27,7 @@ export interface CrossConnectStatus {
     /**
       * The light level of the cross-connect (in dBm).
   * <p>
-  Example: `14.0`
+  Example: {@code 14.0}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "lightLevelIndBm"?: number;
@@ -57,7 +57,7 @@ export interface CrossConnectStatus {
     /**
       * The light levels of the cross-connect (in dBm).
   * <p>
-  Example: `[14.0, -14.0, 2.1, -10.1]`
+  Example: {@code [14.0, -14.0, 2.1, -10.1]}
   *
       */
     "lightLevelsInDBm"?: Array<number>;

package/lib/model/cross-connect.d.ts

@@ -25,7 +25,7 @@ Oracle recommends you create each cross-connect in a
 * <p>
 **Note:** If you're a provider who is setting up a physical connection to Oracle so customers
 * can use FastConnect over the connection, be aware that your connection is modeled the
-* same way as a colocated customer's (with `CrossConnect` and `CrossConnectGroup` objects, and so on).
+* same way as a colocated customer's (with {@code CrossConnect} and {@code CrossConnectGroup} objects, and so on).
 * <p>
 To use any of the API operations, you must be authorized in an IAM policy. If you're not authorized,
 * talk to an administrator. If you're an administrator who needs to write policies to give users access, see
@@ -44,7 +44,7 @@ export interface CrossConnect {
     "crossConnectGroupId"?: string;
     /**
      * Defined tags for this resource. Each key is predefined and scoped to a namespace.
-     * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
+     * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
      *
      */
     "definedTags"?: {
@@ -60,7 +60,7 @@ export interface CrossConnect {
     "displayName"?: string;
     /**
      * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
-     * Example: `{\"bar-key\": \"value\"}`
+     * Example: {@code {\"bar-key\": \"value\"}}
      *
      */
     "freeformTags"?: {
@@ -86,7 +86,7 @@ export interface CrossConnect {
     /**
       * The port speed for this cross-connect.
   * <p>
-  Example: `10 Gbps`
+  Example: {@code 10 Gbps}
   *
       */
     "portSpeedShapeName"?: string;
@@ -99,7 +99,7 @@ export interface CrossConnect {
     /**
       * The date and time the cross-connect was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
   * <p>
-  Example: `2016-08-25T21:10:29.600Z`
+  Example: {@code 2016-08-25T21:10:29.600Z}
   *
       */
     "timeCreated"?: Date;

package/lib/model/dhcp-dns-option.d.ts

@@ -21,7 +21,7 @@ import * as model from "../model";
  */
 export interface DhcpDnsOption extends model.DhcpOption {
     /**
-     * If you set `serverType` to `CustomDnsServer`, specify the
+     * If you set {@code serverType} to {@code CustomDnsServer}, specify the
      * IP address of at least one DNS server of your choice (three maximum).
      *
      */

package/lib/model/dhcp-options.d.ts

@@ -38,7 +38,7 @@ export interface DhcpOptions {
     "compartmentId": string;
     /**
      * Defined tags for this resource. Each key is predefined and scoped to a namespace.
-     * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
+     * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
      *
      */
     "definedTags"?: {
@@ -54,7 +54,7 @@ export interface DhcpOptions {
     "displayName"?: string;
     /**
      * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
-     * Example: `{\"bar-key\": \"value\"}`
+     * Example: {@code {\"bar-key\": \"value\"}}
      *
      */
     "freeformTags"?: {
@@ -75,7 +75,7 @@ export interface DhcpOptions {
     /**
       * Date and time the set of DHCP options was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
   * <p>
-  Example: `2016-08-25T21:10:29.600Z`
+  Example: {@code 2016-08-25T21:10:29.600Z}
   *
       */
     "timeCreated": Date;

package/lib/model/dhcp-search-domain-option.d.ts

@@ -24,10 +24,10 @@ export interface DhcpSearchDomainOption extends model.DhcpOption {
   * and [RFC 1123](https://tools.ietf.org/html/rfc1123). During a DNS query,
   * the OS will append this search domain name to the value being queried.
   * <p>
-  If you set {@link DhcpDnsOption} to `VcnLocalPlusInternet`,
+  If you set {@link DhcpDnsOption} to {@code VcnLocalPlusInternet},
   * and you assign a DNS label to the VCN during creation, the search domain name in the
   * VCN's default set of DHCP options is automatically set to the VCN domain
-  * (for example, `vcn1.oraclevcn.com`).
+  * (for example, {@code vcn1.oraclevcn.com}).
   * <p>
   If you don't want to use a search domain name, omit this option from the
   * set of DHCP options. Do not include this option with an empty list

package/lib/model/drg-attachment-info.d.ts

@@ -13,7 +13,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
  * This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.
  */
 /**
- * The `DrgAttachmentInfo` resource contains the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the DRG attachment.
+ * The {@code DrgAttachmentInfo} resource contains the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the DRG attachment.
  *
  */
 export interface DrgAttachmentInfo {

package/lib/model/drg-attachment.d.ts

@@ -46,7 +46,7 @@ export interface DrgAttachment {
     /**
       * The date and time the DRG attachment was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
   * <p>
-  Example: `2016-08-25T21:10:29.600Z`
+  Example: {@code 2016-08-25T21:10:29.600Z}
   *
       */
     "timeCreated"?: Date;
@@ -60,7 +60,7 @@ export interface DrgAttachment {
     "networkDetails"?: model.VcnDrgAttachmentNetworkDetails | model.LoopBackDrgAttachmentNetworkDetails | model.IpsecTunnelDrgAttachmentNetworkDetails | model.VirtualCircuitDrgAttachmentNetworkDetails | model.RemotePeeringConnectionDrgAttachmentNetworkDetails;
     /**
      * Defined tags for this resource. Each key is predefined and scoped to a namespace.
-     * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
+     * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
      *
      */
     "definedTags"?: {
@@ -70,7 +70,7 @@ export interface DrgAttachment {
     };
     /**
      * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
-     * Example: `{\"bar-key\": \"value\"}`
+     * Example: {@code {\"bar-key\": \"value\"}}
      *
      */
     "freeformTags"?: {
@@ -84,13 +84,13 @@ export interface DrgAttachment {
     * [Transit Routing: Access to Multiple VCNs in Same Region](https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/transitrouting.htm)
   *   * [Transit Routing: Private Access to Oracle Services](https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/transitroutingoracleservices.htm)
   * <p>
-  This field is deprecated. Instead, use the `networkDetails` field to view the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the attached resource.
+  This field is deprecated. Instead, use the {@code networkDetails} field to view the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the attached resource.
   *
       */
     "routeTableId"?: string;
     /**
      * The [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the VCN.
-     * This field is deprecated. Instead, use the `networkDetails` field to view the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the attached resource.
+     * This field is deprecated. Instead, use the {@code networkDetails} field to view the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the attached resource.
      *
      */
     "vcnId"?: string;
@@ -104,7 +104,7 @@ export interface DrgAttachment {
     /**
       * Indicates whether the DRG attachment and attached network live in a different tenancy than the DRG.
   * <p>
-  Example: `false`
+  Example: {@code false}
   *
       */
     "isCrossTenancy"?: boolean;

package/lib/model/drg-route-distribution-statement.d.ts

@@ -26,7 +26,7 @@ export interface DrgRouteDistributionStatement {
      */
     "matchCriteria": Array<model.DrgRouteDistributionMatchCriteria>;
     /**
-     * `ACCEPT` indicates the route should be imported or exported as-is.
+     * {@code ACCEPT} indicates the route should be imported or exported as-is.
      *
      */
     "action": DrgRouteDistributionStatement.Action;

package/lib/model/drg-route-distribution.d.ts

@@ -15,7 +15,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
 /**
 * A route distribution establishes how routes get imported into DRG route tables and exported through the DRG attachments.
 * <p>
-A route distribution is a list of statements. Each statement consists of a set of matches, all of which must be `True` in order for
+A route distribution is a list of statements. Each statement consists of a set of matches, all of which must be {@code True} in order for
 * the statement's action to take place. Each statement determines which routes are propagated.
 * <p>
 You can assign a route distribution as a route table's import distribution. The statements in an import
@@ -48,7 +48,7 @@ export interface DrgRouteDistribution {
     "compartmentId": string;
     /**
      * Defined tags for this resource. Each key is predefined and scoped to a namespace.
-     * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
+     * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
      *
      */
     "definedTags"?: {
@@ -64,7 +64,7 @@ export interface DrgRouteDistribution {
     "displayName"?: string;
     /**
      * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
-     * Example: `{\"bar-key\": \"value\"}`
+     * Example: {@code {\"bar-key\": \"value\"}}
      *
      */
     "freeformTags"?: {
@@ -81,7 +81,7 @@ export interface DrgRouteDistribution {
     /**
       * The date and time the route distribution was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
   * <p>
-  Example: `2016-08-25T21:10:29.600Z`
+  Example: {@code 2016-08-25T21:10:29.600Z}
   *
       */
     "timeCreated": Date;

package/lib/model/drg-route-rule.d.ts

@@ -23,10 +23,10 @@ export interface DrgRouteRule {
       * Represents the range of IP addresses to match against when routing traffic.
   * <p>
   Potential values:
-  *   * An IP address range (IPv4 or IPv6) in CIDR notation. For example: `192.168.1.0/24`
-  *   or `2001:0db8:0123:45::/56`.
-  *   * When you're setting up a security rule for traffic destined for a particular `Service` through
-  *   a service gateway, this is the `cidrBlock` value associated with that {@link Service}. For example: `oci-phx-objectstorage`.
+  *   * An IP address range (IPv4 or IPv6) in CIDR notation. For example: {@code 192.168.1.0/24}
+  *   or {@code 2001:0db8:0123:45::/56}.
+  *   * When you're setting up a security rule for traffic destined for a particular {@code Service} through
+  *   a service gateway, this is the {@code cidrBlock} value associated with that {@link Service}. For example: {@code oci-phx-objectstorage}.
   *
       */
     "destination": string;
@@ -35,10 +35,10 @@ export interface DrgRouteRule {
   * <p>
   Allowed values:
   * <p>
-    * `CIDR_BLOCK`: If the rule's `destination` is an IP address range in CIDR notation.
-  *   * `SERVICE_CIDR_BLOCK`: If the rule's `destination` is the `cidrBlock` value for a
+    * {@code CIDR_BLOCK}: If the rule's {@code destination} is an IP address range in CIDR notation.
+  *   * {@code SERVICE_CIDR_BLOCK}: If the rule's {@code destination} is the {@code cidrBlock} value for a
   *     {@link Service} (the rule is for traffic destined for a
-  *     particular `Service` through a service gateway).
+  *     particular {@code Service} through a service gateway).
   *
       */
     "destinationType": DrgRouteRule.DestinationType;
@@ -46,7 +46,7 @@ export interface DrgRouteRule {
       * The [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the next hop DRG attachment responsible
   * for reaching the network destination.
   * <p>
-  A value of `BLACKHOLE` means traffic for this route is discarded without notification.
+  A value of {@code BLACKHOLE} means traffic for this route is discarded without notification.
   *
       */
     "nextHopDrgAttachmentId": string;
@@ -73,10 +73,10 @@ export interface DrgRouteRule {
     "id": string;
     /**
       * The earliest origin of a route. If a route is advertised to a DRG through an IPsec tunnel attachment,
-  * and is propagated to peered DRGs via RPC attachments, the route's provenance in the peered DRGs remains `IPSEC_TUNNEL`,
+  * and is propagated to peered DRGs via RPC attachments, the route's provenance in the peered DRGs remains {@code IPSEC_TUNNEL},
   * because that is the earliest origin.
   * <p>
-  No routes with a provenance `IPSEC_TUNNEL` or `VIRTUAL_CIRCUIT` will be exported to IPsec tunnel or virtual circuit attachments,
+  No routes with a provenance {@code IPSEC_TUNNEL} or {@code VIRTUAL_CIRCUIT} will be exported to IPsec tunnel or virtual circuit attachments,
   * regardless of the attachment's export distribution.
   *
       */

package/lib/model/drg-route-table.d.ts

@@ -19,7 +19,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
 * The routing decision for a packet entering a DRG is determined by the rules in the DRG route table
 * assigned to the attachment-of-entry.
 * <p>
-Each DRG attachment can inject routes in any DRG route table, provided there is a statement corresponding to the attachment in the route table's `importDrgRouteDistribution`.
+Each DRG attachment can inject routes in any DRG route table, provided there is a statement corresponding to the attachment in the route table's {@code importDrgRouteDistribution}.
 * You can also insert static routes into the DRG route tables.
 * <p>
 The DRG route table is always in the same compartment as the DRG. There must always be a default
@@ -46,7 +46,7 @@ export interface DrgRouteTable {
     "drgId": string;
     /**
      * Defined tags for this resource. Each key is predefined and scoped to a namespace.
-     * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
+     * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
      *
      */
     "definedTags"?: {
@@ -62,7 +62,7 @@ export interface DrgRouteTable {
     "displayName"?: string;
     /**
      * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
-     * Example: `{\"bar-key\": \"value\"}`
+     * Example: {@code {\"bar-key\": \"value\"}}
      *
      */
     "freeformTags"?: {
@@ -71,7 +71,7 @@ export interface DrgRouteTable {
     /**
       * The date and time the DRG route table was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
   * <p>
-  Example: `2016-08-25T21:10:29.600Z`
+  Example: {@code 2016-08-25T21:10:29.600Z}
   *
       */
     "timeCreated": Date;

package/lib/model/drg.d.ts

@@ -32,7 +32,7 @@ export interface Drg {
     "compartmentId": string;
     /**
      * Defined tags for this resource. Each key is predefined and scoped to a namespace.
-     * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
+     * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
      *
      */
     "definedTags"?: {
@@ -48,7 +48,7 @@ export interface Drg {
     "displayName"?: string;
     /**
      * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
-     * Example: `{\"bar-key\": \"value\"}`
+     * Example: {@code {\"bar-key\": \"value\"}}
      *
      */
     "freeformTags"?: {
@@ -65,7 +65,7 @@ export interface Drg {
     /**
       * The date and time the DRG was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
   * <p>
-  Example: `2016-08-25T21:10:29.600Z`
+  Example: {@code 2016-08-25T21:10:29.600Z}
   *
       */
     "timeCreated"?: Date;

package/lib/model/egress-security-rule.d.ts

@@ -23,26 +23,26 @@ export interface EgressSecurityRule {
   * <p>
   Allowed values:
   * <p>
-    * IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56`
+    * IP address range in CIDR notation. For example: {@code 192.168.1.0/24} or {@code 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).
   * <p>
-    * The `cidrBlock` value for a {@link 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`.
+    * The {@code cidrBlock} value for a {@link Service}, if you're
+  *     setting up a security list rule for traffic destined for a particular {@code Service} through
+  *     a service gateway. For example: {@code oci-phx-objectstorage}.
   *
       */
     "destination": string;
     /**
-      * Type of destination for the rule. The default is `CIDR_BLOCK`.
+      * Type of destination for the rule. The default is {@code CIDR_BLOCK}.
   * <p>
   Allowed values:
   * <p>
-    * `CIDR_BLOCK`: If the rule's `destination` is an IP address range in CIDR notation.
+    * {@code CIDR_BLOCK}: If the rule's {@code destination} is an IP address range in CIDR notation.
   * <p>
-    * `SERVICE_CIDR_BLOCK`: If the rule's `destination` is the `cidrBlock` value for a
+    * {@code SERVICE_CIDR_BLOCK}: If the rule's {@code destination} is the {@code cidrBlock} value for a
   *     {@link Service} (the rule is for traffic destined for a
-  *     particular `Service` through a service gateway).
+  *     particular {@code Service} through a service gateway).
   *
       */
     "destinationType"?: EgressSecurityRule.DestinationType;
@@ -57,7 +57,7 @@ export interface EgressSecurityRule {
      */
     "isStateless"?: boolean;
     /**
-     * The transport protocol. Specify either `all` or an IPv4 protocol number as
+     * The transport protocol. Specify either {@code all} or an IPv4 protocol number as
      * defined in
      * [Protocol Numbers](http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml).
      * Options are supported only for ICMP (\"1\"), TCP (\"6\"), UDP (\"17\"), and ICMPv6 (\"58\").

package/lib/model/endpoint.d.ts

@@ -13,7 +13,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
  * This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.
  */
 /**
- * Information describing a source or destination in a `PathAnalyzerTest` resource.
+ * Information describing a source or destination in a {@code PathAnalyzerTest} resource.
  *
  */
 export interface Endpoint {

package/lib/model/fast-connect-provider-service-key.d.ts

@@ -20,7 +20,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
 export interface FastConnectProviderServiceKey {
     /**
      * The service key that the provider gives you when you set up a virtual circuit connection
-     * from the provider to Oracle Cloud Infrastructure. Use this value as the `providerServiceKeyName`
+     * from the provider to Oracle Cloud Infrastructure. Use this value as the {@code providerServiceKeyName}
      * query parameter for
      * {@link #getFastConnectProviderServiceKey(GetFastConnectProviderServiceKeyRequest) getFastConnectProviderServiceKey}.
      *
@@ -31,7 +31,7 @@ export interface FastConnectProviderServiceKey {
   * available bandwidth levels (that is, shapes), see
   * {@link #listFastConnectProviderVirtualCircuitBandwidthShapes(ListFastConnectProviderVirtualCircuitBandwidthShapesRequest) listFastConnectProviderVirtualCircuitBandwidthShapes}.
   * <p>
-  Example: `10 Gbps`
+  Example: {@code 10 Gbps}
   *
       */
     "bandwidthShapeName"?: string;

package/lib/model/fast-connect-provider-service.d.ts

@@ -23,7 +23,7 @@ export interface FastConnectProviderService {
   * about the provider service, create a virtual circuit connection from the provider to Oracle
   * Cloud Infrastructure, and retrieve your provider service key for that virtual circuit connection.
   * <p>
-  Example: `https://example.com`
+  Example: {@code https://example.com}
   *
       */
     "description"?: string;

package/lib/model/flow-log-capture-filter-rule-details.d.ts

@@ -52,7 +52,7 @@ export interface FlowLogCaptureFilterRuleDetails {
     "tcpOptions"?: model.TcpOptions;
     "udpOptions"?: model.UdpOptions;
     /**
-     * Type or types of flow logs to store. `ALL` includes records for both accepted traffic and
+     * Type or types of flow logs to store. {@code ALL} includes records for both accepted traffic and
      * rejected traffic.
      *
      */

package/lib/model/i-psec-connection-device-status.d.ts

@@ -30,7 +30,7 @@ export interface IPSecConnectionDeviceStatus {
     /**
       * The date and time the IPSec connection was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
   * <p>
-  Example: `2016-08-25T21:10:29.600Z`
+  Example: {@code 2016-08-25T21:10:29.600Z}
   *
       */
     "timeCreated"?: Date;

package/lib/model/i-psec-connection-tunnel.d.ts

@@ -32,14 +32,14 @@ export interface IPSecConnectionTunnel {
     /**
       * The IP address of the Oracle VPN headend for the connection.
   * <p>
-  Example: `203.0.113.21`
+  Example: {@code 203.0.113.21}
   *
       */
     "vpnIp"?: string;
     /**
       * The IP address of the CPE device's VPN headend.
   * <p>
-  Example: `203.0.113.22`
+  Example: {@code 203.0.113.22}
   *
       */
     "cpeIp"?: string;
@@ -72,14 +72,14 @@ export interface IPSecConnectionTunnel {
     /**
       * The date and time the IPSec tunnel was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
   * <p>
-  Example: `2016-08-25T21:10:29.600Z`
+  Example: {@code 2016-08-25T21:10:29.600Z}
   *
       */
     "timeCreated"?: Date;
     /**
       * When the status of the IPSec tunnel last changed, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
   * <p>
-  Example: `2016-08-25T21:10:29.600Z`
+  Example: {@code 2016-08-25T21:10:29.600Z}
   *
       */
     "timeStatusUpdated"?: Date;
@@ -89,13 +89,13 @@ export interface IPSecConnectionTunnel {
      */
     "oracleCanInitiate"?: IPSecConnectionTunnel.OracleCanInitiate;
     /**
-      * By default (the `AUTO` setting), IKE sends packets with a source and destination port set to 500,
+      * By default (the {@code AUTO} setting), IKE sends packets with a source and destination port set to 500,
   * and when it detects that the port used to forward packets has changed (most likely because a NAT device
   * is between the CPE device and the Oracle VPN headend) it will try to negotiate the use of NAT-T.
   * <p>
-  The `ENABLED` option sets the IKE protocol to use port 4500 instead of 500 and forces encapsulating traffic with the ESP protocol inside UDP packets.
+  The {@code ENABLED} option sets the IKE protocol to use port 4500 instead of 500 and forces encapsulating traffic with the ESP protocol inside UDP packets.
   * <p>
-  The `DISABLED` option directs IKE to completely refuse to negotiate NAT-T
+  The {@code DISABLED} option directs IKE to completely refuse to negotiate NAT-T
   * even if it senses there may be a NAT device in use.
   * <p>