oci-dns 2.76.1 → 2.77.0

package/lib/model/dynect-migration-details.d.ts

@@ -34,7 +34,7 @@ export interface DynectMigrationDetails {
      */
     "password": string;
     /**
-     * A map of fully-qualified domain names (FQDNs) to an array of `MigrationReplacement` objects.
+     * A map of fully-qualified domain names (FQDNs) to an array of {@code MigrationReplacement} objects.
      *
      */
     "httpRedirectReplacements"?: {

package/lib/model/external-downstream.d.ts

@@ -14,7 +14,7 @@ For more information, see [Overview of the DNS Service](/iaas/Content/DNS/Concep
  */
 /**
  * External downstream nameserver for the zone.
- * This field is currently not supported when `zoneType` is `SECONDARY` or `scope` is `PRIVATE`.
+ * This field is currently not supported when {@code zoneType} is {@code SECONDARY} or {@code scope} is {@code PRIVATE}.
  *
  */
 export interface ExternalDownstream {

package/lib/model/migration-replacement.d.ts

@@ -23,7 +23,7 @@ export interface MigrationReplacement {
      */
     "rtype": string;
     /**
-     * The canonical name for a substitute type of the replacement record to be used if the specified `rtype` is not allowed at the domain. The specified `ttl` and `rdata` will still apply with the substitute type.
+     * The canonical name for a substitute type of the replacement record to be used if the specified {@code rtype} is not allowed at the domain. The specified {@code ttl} and {@code rdata} will still apply with the substitute type.
      */
     "substituteRtype"?: string;
     /**

package/lib/model/record-operation.d.ts

@@ -15,7 +15,7 @@ For more information, see [Overview of the DNS Service](/iaas/Content/DNS/Concep
 /**
  * An extension of the existing record resource, describing either a
  * precondition, an add, or a remove. Preconditions check all fields,
- * including read-only data like `recordHash` and `rrsetVersion`.
+ * including read-only data like {@code recordHash} and {@code rrsetVersion}.
  *
  */
 export interface RecordOperation {
@@ -63,22 +63,22 @@ export interface RecordOperation {
       * A description of how a record relates to a PATCH operation.
   * <p>
   
-  * - `REQUIRE` indicates a precondition that record data **must** already exist.
-  * - `PROHIBIT` indicates a precondition that record data **must not** already exist.
-  * - `ADD` indicates that record data **must** exist after successful application.
-  * - `REMOVE` indicates that record data **must not** exist after successful application.
+  * - {@code REQUIRE} indicates a precondition that record data **must** already exist.
+  * - {@code PROHIBIT} indicates a precondition that record data **must not** already exist.
+  * - {@code ADD} indicates that record data **must** exist after successful application.
+  * - {@code REMOVE} indicates that record data **must not** exist after successful application.
   * <p>
   
-  *   **Note:** `ADD` and `REMOVE` operations can succeed even if
+  *   **Note:** {@code ADD} and {@code REMOVE} operations can succeed even if
   *   they require no changes when applied, such as when the described
   *   records are already present or absent.
   * <p>
   
-  *   **Note:** `ADD` and `REMOVE` operations can describe changes for
+  *   **Note:** {@code ADD} and {@code REMOVE} operations can describe changes for
   *   more than one record.
   * <p>
   
-  *   **Example:** `{ \"domain\": \"www.example.com\", \"rtype\": \"AAAA\", \"ttl\": 60 }`
+  *   **Example:** {@code { \"domain\": \"www.example.com\", \"rtype\": \"AAAA\", \"ttl\": 60 }}
   *   specifies a new TTL for every record in the www.example.com AAAA RRSet.
   *
       */

package/lib/model/resolver-endpoint-summary.d.ts

@@ -56,7 +56,7 @@ export interface ResolverEndpointSummary {
      * The date and time the resource was created in \"YYYY-MM-ddThh:mm:ssZ\" format
      * with a Z offset, as defined by RFC 3339.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeCreated": Date;
@@ -64,7 +64,7 @@ export interface ResolverEndpointSummary {
      * The date and time the resource was last updated in \"YYYY-MM-ddThh:mm:ssZ\"
      * format with a Z offset, as defined by RFC 3339.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeUpdated": Date;

package/lib/model/resolver-endpoint.d.ts

@@ -56,7 +56,7 @@ export interface ResolverEndpoint {
      * The date and time the resource was created in \"YYYY-MM-ddThh:mm:ssZ\" format
      * with a Z offset, as defined by RFC 3339.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeCreated": Date;
@@ -64,7 +64,7 @@ export interface ResolverEndpoint {
      * The date and time the resource was last updated in \"YYYY-MM-ddThh:mm:ssZ\"
      * format with a Z offset, as defined by RFC 3339.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeUpdated": Date;

package/lib/model/resolver-summary.d.ts

@@ -42,7 +42,7 @@ export interface ResolverSummary {
   * For more information, see [Resource Tags](https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
   * <p>
   
-  * **Example:** `{\"Department\": \"Finance\"}`
+  * **Example:** {@code {\"Department\": \"Finance\"}}
   *
       */
     "freeformTags": {
@@ -53,7 +53,7 @@ export interface ResolverSummary {
   * For more information, see [Resource Tags](https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
   * <p>
   
-  * **Example:** `{\"Operations\": {\"CostCenter\": \"42\"}}`
+  * **Example:** {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
   *
       */
     "definedTags": {
@@ -69,7 +69,7 @@ export interface ResolverSummary {
      * The date and time the resource was created in \"YYYY-MM-ddThh:mm:ssZ\" format
      * with a Z offset, as defined by RFC 3339.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeCreated": Date;
@@ -77,7 +77,7 @@ export interface ResolverSummary {
      * The date and time the resource was last updated in \"YYYY-MM-ddThh:mm:ssZ\"
      * format with a Z offset, as defined by RFC 3339.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeUpdated": Date;

package/lib/model/resolver.d.ts

@@ -43,7 +43,7 @@ export interface Resolver {
   * For more information, see [Resource Tags](https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
   * <p>
   
-  * **Example:** `{\"Department\": \"Finance\"}`
+  * **Example:** {@code {\"Department\": \"Finance\"}}
   *
       */
     "freeformTags": {
@@ -54,7 +54,7 @@ export interface Resolver {
   * For more information, see [Resource Tags](https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
   * <p>
   
-  * **Example:** `{\"Operations\": {\"CostCenter\": \"42\"}}`
+  * **Example:** {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
   *
       */
     "definedTags": {
@@ -70,7 +70,7 @@ export interface Resolver {
      * The date and time the resource was created in \"YYYY-MM-ddThh:mm:ssZ\" format
      * with a Z offset, as defined by RFC 3339.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeCreated": Date;
@@ -78,7 +78,7 @@ export interface Resolver {
      * The date and time the resource was last updated in \"YYYY-MM-ddThh:mm:ssZ\"
      * format with a Z offset, as defined by RFC 3339.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeUpdated": Date;

package/lib/model/steering-policy-answer.d.ts

@@ -22,8 +22,8 @@ For more information, see [Overview of the DNS Service](/iaas/Content/DNS/Concep
 export interface SteeringPolicyAnswer {
     /**
       * A user-friendly name for the answer, unique within the steering policy.
-  * An answer's `name` property can be referenced in `answerCondition` properties
-  * of rules using `answer.name`.
+  * An answer's {@code name} property can be referenced in {@code answerCondition} properties
+  * of rules using {@code answer.name}.
   * <p>
   **Example:**
   * <p>
@@ -57,8 +57,8 @@ export interface SteeringPolicyAnswer {
     "rdata": string;
     /**
       * The freeform name of a group of one or more records in which this record is included,
-  * such as \"LAX data center\". An answer's `pool` property can be referenced in `answerCondition`
-  * properties of rules using `answer.pool`.
+  * such as \"LAX data center\". An answer's {@code pool} property can be referenced in {@code answerCondition}
+  * properties of rules using {@code answer.pool}.
   * <p>
   **Example:**
   * <p>
@@ -77,9 +77,9 @@ export interface SteeringPolicyAnswer {
       */
     "pool"?: string;
     /**
-     * Set this property to `true` to indicate that the answer is administratively disabled,
-     * such as when the corresponding server is down for maintenance. An answer's `isDisabled`
-     * property can be referenced in `answerCondition` properties in rules using `answer.isDisabled`.
+     * Set this property to {@code true} to indicate that the answer is administratively disabled,
+     * such as when the corresponding server is down for maintenance. An answer's {@code isDisabled}
+     * property can be referenced in {@code answerCondition} properties in rules using {@code answer.isDisabled}.
      * <p>
      **Example:**
      *   \"rules\": [

package/lib/model/steering-policy-attachment-summary.d.ts

@@ -57,7 +57,7 @@ export interface SteeringPolicyAttachmentSummary {
     /**
      * The date and time the resource was created, expressed in RFC 3339 timestamp format.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeCreated": Date;

package/lib/model/steering-policy-attachment.d.ts

@@ -63,7 +63,7 @@ export interface SteeringPolicyAttachment {
     /**
      * The date and time the resource was created, expressed in RFC 3339 timestamp format.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeCreated": Date;

package/lib/model/steering-policy-filter-answer-data.d.ts

@@ -19,7 +19,7 @@ export interface SteeringPolicyFilterAnswerData {
      */
     "answerCondition"?: string;
     /**
-     * Keeps the answer only if the value is `true`.
+     * Keeps the answer only if the value is {@code true}.
      */
     "shouldKeep"?: boolean;
 }

package/lib/model/steering-policy-filter-rule-case.d.ts

@@ -18,14 +18,14 @@ export interface SteeringPolicyFilterRuleCase {
      * An expression that uses conditions at the time of a DNS query to indicate
      * whether a case matches. Conditions may include the geographical location, IP
      * subnet, or ASN the DNS query originated. **Example:** If you have an
-     * office that uses the subnet `192.0.2.0/24` you could use a `caseCondition`
-     * expression `query.client.address in ('192.0.2.0/24')` to define a case that
+     * office that uses the subnet {@code 192.0.2.0/24} you could use a {@code caseCondition}
+     * expression {@code query.client.address in ('192.0.2.0/24')} to define a case that
      * matches queries from that office.
      *
      */
     "caseCondition"?: string;
     /**
-     * An array of `SteeringPolicyFilterAnswerData` objects.
+     * An array of {@code SteeringPolicyFilterAnswerData} objects.
      */
     "answerData"?: Array<model.SteeringPolicyFilterAnswerData>;
 }

package/lib/model/steering-policy-filter-rule.d.ts

@@ -15,21 +15,21 @@ For more information, see [Overview of the DNS Service](/iaas/Content/DNS/Concep
 import * as model from "../model";
 export interface SteeringPolicyFilterRule extends model.SteeringPolicyRule {
     /**
-     * An array of `caseConditions`. A rule may optionally include a sequence of cases defining alternate
+     * An array of {@code caseConditions}. A rule may optionally include a sequence of cases defining alternate
      * configurations for how it should behave during processing for any given DNS query. When a rule has
-     * no sequence of `cases`, it is always evaluated with the same configuration during processing. When
-     * a rule has an empty sequence of `cases`, it is always ignored during processing. When a rule has a
-     * non-empty sequence of `cases`, its behavior during processing is configured by the first matching
-     * `case` in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
-     * `caseCondition` always matches. A rule case with a `caseCondition` matches only when that expression
+     * no sequence of {@code cases}, it is always evaluated with the same configuration during processing. When
+     * a rule has an empty sequence of {@code cases}, it is always ignored during processing. When a rule has a
+     * non-empty sequence of {@code cases}, its behavior during processing is configured by the first matching
+     * {@code case} in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
+     * {@code caseCondition} always matches. A rule case with a {@code caseCondition} matches only when that expression
      * evaluates to true for the given query.
      *
      */
     "cases"?: Array<model.SteeringPolicyFilterRuleCase>;
     /**
      * Defines a default set of answer conditions and values that are applied to an answer when
-     * `cases` is not defined for the rule, or a matching case does not have any matching
-     * `answerCondition`s in its `answerData`. `defaultAnswerData` is not applied if `cases` is
+     * {@code cases} is not defined for the rule, or a matching case does not have any matching
+     * {@code answerCondition}s in its {@code answerData}. {@code defaultAnswerData} is not applied if {@code cases} is
      * defined and there are no matching cases. In this scenario, the next rule will be processed.
      *
      */

package/lib/model/steering-policy-health-rule-case.d.ts

@@ -17,8 +17,8 @@ export interface SteeringPolicyHealthRuleCase {
      * An expression that uses conditions at the time of a DNS query to indicate
      * whether a case matches. Conditions may include the geographical location, IP
      * subnet, or ASN the DNS query originated. **Example:** If you have an
-     * office that uses the subnet `192.0.2.0/24` you could use a `caseCondition`
-     * expression `query.client.address in ('192.0.2.0/24')` to define a case that
+     * office that uses the subnet {@code 192.0.2.0/24} you could use a {@code caseCondition}
+     * expression {@code query.client.address in ('192.0.2.0/24')} to define a case that
      * matches queries from that office.
      *
      */

package/lib/model/steering-policy-health-rule.d.ts

@@ -15,13 +15,13 @@ For more information, see [Overview of the DNS Service](/iaas/Content/DNS/Concep
 import * as model from "../model";
 export interface SteeringPolicyHealthRule extends model.SteeringPolicyRule {
     /**
-     * An array of `caseConditions`. A rule may optionally include a sequence of cases defining alternate
+     * An array of {@code caseConditions}. A rule may optionally include a sequence of cases defining alternate
      * configurations for how it should behave during processing for any given DNS query. When a rule has
-     * no sequence of `cases`, it is always evaluated with the same configuration during processing. When
-     * a rule has an empty sequence of `cases`, it is always ignored during processing. When a rule has a
-     * non-empty sequence of `cases`, its behavior during processing is configured by the first matching
-     * `case` in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
-     * `caseCondition` always matches. A rule case with a `caseCondition` matches only when that expression
+     * no sequence of {@code cases}, it is always evaluated with the same configuration during processing. When
+     * a rule has an empty sequence of {@code cases}, it is always ignored during processing. When a rule has a
+     * non-empty sequence of {@code cases}, its behavior during processing is configured by the first matching
+     * {@code case} in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
+     * {@code caseCondition} always matches. A rule case with a {@code caseCondition} matches only when that expression
      * evaluates to true for the given query.
      *
      */

package/lib/model/steering-policy-limit-rule-case.d.ts

@@ -17,15 +17,15 @@ export interface SteeringPolicyLimitRuleCase {
      * An expression that uses conditions at the time of a DNS query to indicate
      * whether a case matches. Conditions may include the geographical location, IP
      * subnet, or ASN the DNS query originated. **Example:** If you have an
-     * office that uses the subnet `192.0.2.0/24` you could use a `caseCondition`
-     * expression `query.client.address in ('192.0.2.0/24')` to define a case that
+     * office that uses the subnet {@code 192.0.2.0/24} you could use a {@code caseCondition}
+     * expression {@code query.client.address in ('192.0.2.0/24')} to define a case that
      * matches queries from that office.
      *
      */
     "caseCondition"?: string;
     /**
      * The number of answers allowed to remain after the limit rule has been processed, keeping only the
-     * first of the remaining answers in the list. Example: If the `count` property is set to `2` and
+     * first of the remaining answers in the list. Example: If the {@code count} property is set to {@code 2} and
      * four answers remain before the limit rule is processed, only the first two answers in the list will
      * remain after the limit rule has been processed.
      *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

package/lib/model/steering-policy-limit-rule.d.ts

@@ -15,20 +15,20 @@ For more information, see [Overview of the DNS Service](/iaas/Content/DNS/Concep
 import * as model from "../model";
 export interface SteeringPolicyLimitRule extends model.SteeringPolicyRule {
     /**
-     * An array of `caseConditions`. A rule may optionally include a sequence of cases defining alternate
+     * An array of {@code caseConditions}. A rule may optionally include a sequence of cases defining alternate
      * configurations for how it should behave during processing for any given DNS query. When a rule has
-     * no sequence of `cases`, it is always evaluated with the same configuration during processing. When
-     * a rule has an empty sequence of `cases`, it is always ignored during processing. When a rule has a
-     * non-empty sequence of `cases`, its behavior during processing is configured by the first matching
-     * `case` in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
-     * `caseCondition` always matches. A rule case with a `caseCondition` matches only when that expression
+     * no sequence of {@code cases}, it is always evaluated with the same configuration during processing. When
+     * a rule has an empty sequence of {@code cases}, it is always ignored during processing. When a rule has a
+     * non-empty sequence of {@code cases}, its behavior during processing is configured by the first matching
+     * {@code case} in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
+     * {@code caseCondition} always matches. A rule case with a {@code caseCondition} matches only when that expression
      * evaluates to true for the given query.
      *
      */
     "cases"?: Array<model.SteeringPolicyLimitRuleCase>;
     /**
-     * Defines a default count if `cases` is not defined for the rule or a matching case does
-     * not define `count`. `defaultCount` is **not** applied if `cases` is defined and there
+     * Defines a default count if {@code cases} is not defined for the rule or a matching case does
+     * not define {@code count}. {@code defaultCount} is **not** applied if {@code cases} is defined and there
      * are no matching cases. In this scenario, the next rule will be processed. If no rules
      * remain to be processed, the answer will be chosen from the remaining list of answers.
      *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

package/lib/model/steering-policy-priority-answer-data.d.ts

@@ -19,9 +19,9 @@ export interface SteeringPolicyPriorityAnswerData {
      */
     "answerCondition"?: string;
     /**
-     * The rank assigned to the set of answers that match the expression in `answerCondition`.
+     * The rank assigned to the set of answers that match the expression in {@code answerCondition}.
      * Answers with the lowest values move to the beginning of the list without changing the
-     * relative order of those with the same value. Answers can be given a value between `0` and `255`.
+     * relative order of those with the same value. Answers can be given a value between {@code 0} and {@code 255}.
      *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
      */
     "value": number;

package/lib/model/steering-policy-priority-rule-case.d.ts

@@ -18,14 +18,14 @@ export interface SteeringPolicyPriorityRuleCase {
      * An expression that uses conditions at the time of a DNS query to indicate
      * whether a case matches. Conditions may include the geographical location, IP
      * subnet, or ASN the DNS query originated. **Example:** If you have an
-     * office that uses the subnet `192.0.2.0/24` you could use a `caseCondition`
-     * expression `query.client.address in ('192.0.2.0/24')` to define a case that
+     * office that uses the subnet {@code 192.0.2.0/24} you could use a {@code caseCondition}
+     * expression {@code query.client.address in ('192.0.2.0/24')} to define a case that
      * matches queries from that office.
      *
      */
     "caseCondition"?: string;
     /**
-     * An array of `SteeringPolicyPriorityAnswerData` objects.
+     * An array of {@code SteeringPolicyPriorityAnswerData} objects.
      */
     "answerData"?: Array<model.SteeringPolicyPriorityAnswerData>;
 }

package/lib/model/steering-policy-priority-rule.d.ts

@@ -15,21 +15,21 @@ For more information, see [Overview of the DNS Service](/iaas/Content/DNS/Concep
 import * as model from "../model";
 export interface SteeringPolicyPriorityRule extends model.SteeringPolicyRule {
     /**
-     * An array of `caseConditions`. A rule may optionally include a sequence of cases defining alternate
+     * An array of {@code caseConditions}. A rule may optionally include a sequence of cases defining alternate
      * configurations for how it should behave during processing for any given DNS query. When a rule has
-     * no sequence of `cases`, it is always evaluated with the same configuration during processing. When
-     * a rule has an empty sequence of `cases`, it is always ignored during processing. When a rule has a
-     * non-empty sequence of `cases`, its behavior during processing is configured by the first matching
-     * `case` in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
-     * `caseCondition` always matches. A rule case with a `caseCondition` matches only when that expression
+     * no sequence of {@code cases}, it is always evaluated with the same configuration during processing. When
+     * a rule has an empty sequence of {@code cases}, it is always ignored during processing. When a rule has a
+     * non-empty sequence of {@code cases}, its behavior during processing is configured by the first matching
+     * {@code case} in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
+     * {@code caseCondition} always matches. A rule case with a {@code caseCondition} matches only when that expression
      * evaluates to true for the given query.
      *
      */
     "cases"?: Array<model.SteeringPolicyPriorityRuleCase>;
     /**
      * Defines a default set of answer conditions and values that are applied to an answer when
-     * `cases` is not defined for the rule or a matching case does not have any matching
-     * `answerCondition`s in its `answerData`. `defaultAnswerData` is not applied if `cases` is
+     * {@code cases} is not defined for the rule or a matching case does not have any matching
+     * {@code answerCondition}s in its {@code answerData}. {@code defaultAnswerData} is not applied if {@code cases} is
      * defined and there are no matching cases. In this scenario, the next rule will be processed.
      *
      */

package/lib/model/steering-policy-rule.d.ts

@@ -17,7 +17,7 @@ For more information, see [Overview of the DNS Service](/iaas/Content/DNS/Concep
 * filter and sort answers based on weight, priority, endpoint health, and other data.
 * <p>
 
-* A rule may optionally include a sequence of cases, each with an optional `caseCondition`
+* A rule may optionally include a sequence of cases, each with an optional {@code caseCondition}
 * expression. Cases allow a sequence of conditions to be defined that will apply different
 * parameters to the rule when the conditions are met. For more information about cases,
 * see [Traffic Management API Guide](https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Concepts/trafficmanagementapi.htm).

package/lib/model/steering-policy-summary.d.ts

@@ -37,8 +37,8 @@ export interface SteeringPolicySummary {
     "ttl": number;
     /**
       * The OCID of the health check monitor providing health data about the answers of the
-  * steering policy. A steering policy answer with `rdata` matching a monitored endpoint
-  * will use the health data of that endpoint. A steering policy answer with `rdata` not
+  * steering policy. A steering policy answer with {@code rdata} matching a monitored endpoint
+  * will use the health data of that endpoint. A steering policy answer with {@code rdata} not
   * matching any monitored endpoint will be assumed healthy.
   * <p>
   
@@ -54,42 +54,42 @@ export interface SteeringPolicySummary {
   * results when answering DNS queries.
   * <p>
   
-  * **Example:** The `FAILOVER` template determines answers by filtering the policy's answers
-  * using the `FILTER` rule first, then the following rules in succession: `HEALTH`, `PRIORITY`,
-  * and `LIMIT`. This gives the domain dynamic failover capability.
+  * **Example:** The {@code FAILOVER} template determines answers by filtering the policy's answers
+  * using the {@code FILTER} rule first, then the following rules in succession: {@code HEALTH}, {@code PRIORITY},
+  * and {@code LIMIT}. This gives the domain dynamic failover capability.
   * <p>
   
-  * It is **strongly recommended** to use a template other than `CUSTOM` when creating
+  * It is **strongly recommended** to use a template other than {@code CUSTOM} when creating
   * a steering policy.
   * <p>
   
-  * All templates require the rule order to begin with an unconditional `FILTER` rule that keeps
-  * answers contingent upon `answer.isDisabled != true`, except for `CUSTOM`. A defined
-  * `HEALTH` rule must follow the `FILTER` rule if the policy references a `healthCheckMonitorId`.
-  * The last rule of a template must must be a `LIMIT` rule. For more information about templates
+  * All templates require the rule order to begin with an unconditional {@code FILTER} rule that keeps
+  * answers contingent upon {@code answer.isDisabled != true}, except for {@code CUSTOM}. A defined
+  * {@code HEALTH} rule must follow the {@code FILTER} rule if the policy references a {@code healthCheckMonitorId}.
+  * The last rule of a template must must be a {@code LIMIT} rule. For more information about templates
   * and code examples, see [Traffic Management API Guide](https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Concepts/trafficmanagementapi.htm).
   * <p>
   **Template Types**
   * <p>
-  * `FAILOVER` - Uses health check information on your endpoints to determine which DNS answers
+  * {@code FAILOVER} - Uses health check information on your endpoints to determine which DNS answers
   * to serve. If an endpoint fails a health check, the answer for that endpoint will be removed
   * from the list of available answers until the endpoint is detected as healthy.
   * <p>
   
-  * * `LOAD_BALANCE` - Distributes web traffic to specified endpoints based on defined weights.
+  * * {@code LOAD_BALANCE} - Distributes web traffic to specified endpoints based on defined weights.
   * <p>
   
-  * * `ROUTE_BY_GEO` - Answers DNS queries based on the query's geographic location. For a list of geographic
+  * * {@code ROUTE_BY_GEO} - Answers DNS queries based on the query's geographic location. For a list of geographic
   * locations to route by, see [Traffic Management Geographic Locations](https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Reference/trafficmanagementgeo.htm).
   * <p>
   
-  * * `ROUTE_BY_ASN` - Answers DNS queries based on the query's originating ASN.
+  * * {@code ROUTE_BY_ASN} - Answers DNS queries based on the query's originating ASN.
   * <p>
   
-  * * `ROUTE_BY_IP` - Answers DNS queries based on the query's IP address.
+  * * {@code ROUTE_BY_IP} - Answers DNS queries based on the query's IP address.
   * <p>
   
-  * * `CUSTOM` - Allows a customized configuration of rules.
+  * * {@code CUSTOM} - Allows a customized configuration of rules.
   *
       */
     "template": SteeringPolicySummary.Template;
@@ -98,7 +98,7 @@ export interface SteeringPolicySummary {
   * For more information, see [Resource Tags](https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
   * <p>
   
-  * **Example:** `{\"Department\": \"Finance\"}`
+  * **Example:** {@code {\"Department\": \"Finance\"}}
   *
       */
     "freeformTags": {
@@ -109,7 +109,7 @@ export interface SteeringPolicySummary {
   * For more information, see [Resource Tags](https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
   * <p>
   
-  * **Example:** `{\"Operations\": {\"CostCenter\": \"42\"}}`
+  * **Example:** {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
   *
       */
     "definedTags": {
@@ -128,7 +128,7 @@ export interface SteeringPolicySummary {
     /**
      * The date and time the resource was created, expressed in RFC 3339 timestamp format.
      * <p>
-     **Example:** `2016-07-22T17:23:59:60Z`
+     **Example:** {@code 2016-07-22T17:23:59:60Z}
      *
      */
     "timeCreated": Date;

package/lib/model/steering-policy-weighted-answer-data.d.ts

@@ -20,7 +20,7 @@ export interface SteeringPolicyWeightedAnswerData {
     "answerCondition"?: string;
     /**
      * The weight assigned to the set of selected answers. Answers with a higher weight will be served
-     * more frequently. Answers can be given a value between `0` and `255`.
+     * more frequently. Answers can be given a value between {@code 0} and {@code 255}.
      *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
      */
     "value": number;

package/lib/model/steering-policy-weighted-rule-case.d.ts

@@ -18,14 +18,14 @@ export interface SteeringPolicyWeightedRuleCase {
      * An expression that uses conditions at the time of a DNS query to indicate
      * whether a case matches. Conditions may include the geographical location, IP
      * subnet, or ASN the DNS query originated. **Example:** If you have an
-     * office that uses the subnet `192.0.2.0/24` you could use a `caseCondition`
-     * expression `query.client.address in ('192.0.2.0/24')` to define a case that
+     * office that uses the subnet {@code 192.0.2.0/24} you could use a {@code caseCondition}
+     * expression {@code query.client.address in ('192.0.2.0/24')} to define a case that
      * matches queries from that office.
      *
      */
     "caseCondition"?: string;
     /**
-     * An array of `SteeringPolicyWeightedAnswerData` objects.
+     * An array of {@code SteeringPolicyWeightedAnswerData} objects.
      */
     "answerData"?: Array<model.SteeringPolicyWeightedAnswerData>;
 }

package/lib/model/steering-policy-weighted-rule.d.ts

@@ -15,21 +15,21 @@ For more information, see [Overview of the DNS Service](/iaas/Content/DNS/Concep
 import * as model from "../model";
 export interface SteeringPolicyWeightedRule extends model.SteeringPolicyRule {
     /**
-     * An array of `caseConditions`. A rule may optionally include a sequence of cases defining alternate
+     * An array of {@code caseConditions}. A rule may optionally include a sequence of cases defining alternate
      * configurations for how it should behave during processing for any given DNS query. When a rule has
-     * no sequence of `cases`, it is always evaluated with the same configuration during processing. When
-     * a rule has an empty sequence of `cases`, it is always ignored during processing. When a rule has a
-     * non-empty sequence of `cases`, its behavior during processing is configured by the first matching
-     * `case` in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
-     * `caseCondition` always matches. A rule case with a `caseCondition` matches only when that expression
+     * no sequence of {@code cases}, it is always evaluated with the same configuration during processing. When
+     * a rule has an empty sequence of {@code cases}, it is always ignored during processing. When a rule has a
+     * non-empty sequence of {@code cases}, its behavior during processing is configured by the first matching
+     * {@code case} in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
+     * {@code caseCondition} always matches. A rule case with a {@code caseCondition} matches only when that expression
      * evaluates to true for the given query.
      *
      */
     "cases"?: Array<model.SteeringPolicyWeightedRuleCase>;
     /**
      * Defines a default set of answer conditions and values that are applied to an answer when
-     * `cases` is not defined for the rule or a matching case does not have any matching
-     * `answerCondition`s in its `answerData`. `defaultAnswerData` is not applied if `cases` is
+     * {@code cases} is not defined for the rule or a matching case does not have any matching
+     * {@code answerCondition}s in its {@code answerData}. {@code defaultAnswerData} is not applied if {@code cases} is
      * defined and there are no matching cases. In this scenario, the next rule will be processed.
      *
      */