oci-loadbalancer 2.76.1 → 2.77.1

package/lib/model/extend-http-request-header-value-rule.d.ts

@@ -25,7 +25,7 @@ This rule adds a prefix, a suffix, or both to the header value.
 *  The system does not support this rule for headers with multiple values.
 * <p>
 *  The system does not distinquish between underscore and dash characters in headers. That is, it treats
-*    `example_header_name` and `example-header-name` as identical.  If two such headers appear in a request, the system
+*    {@code example_header_name} and {@code example-header-name} as identical.  If two such headers appear in a request, the system
 *    applies the action to the first header it finds. The affected header cannot be determined in advance. Oracle
 *    recommends that you do not rely on underscore or dash characters to uniquely distinguish header names.
 *
@@ -34,27 +34,27 @@ export interface ExtendHttpRequestHeaderValueRule extends model.Rule {
     /**
       * A header name that conforms to RFC 7230.
   * <p>
-  Example: `example_header_name`
+  Example: {@code example_header_name}
   *
       */
     "header": string;
     /**
       * A string to prepend to the header value. The resulting header value must conform to RFC 7230.
   * With the following exceptions:
-  * *  value cannot contain `$`
-  * *  value cannot contain patterns like `{variable_name}`. They are reserved for future extensions. Currently, such values are invalid.
+  * *  value cannot contain {@code $}
+  * *  value cannot contain patterns like {@code {variable_name}}. They are reserved for future extensions. Currently, such values are invalid.
   * <p>
-  Example: `example_prefix_value`
+  Example: {@code example_prefix_value}
   *
       */
     "prefix"?: string;
     /**
       * A string to append to the header value. The resulting header value must conform to RFC 7230.
   * With the following exceptions:
-  * *  value cannot contain `$`
-  * *  value cannot contain patterns like `{variable_name}`. They are reserved for future extensions. Currently, such values are invalid.
+  * *  value cannot contain {@code $}
+  * *  value cannot contain patterns like {@code {variable_name}}. They are reserved for future extensions. Currently, such values are invalid.
   * <p>
-  Example: `example_suffix_value`
+  Example: {@code example_suffix_value}
   *
       */
     "suffix"?: string;

package/lib/model/extend-http-response-header-value-rule.d.ts

@@ -25,7 +25,7 @@ This rule adds a prefix, a suffix, or both to the header value.
 *  The system does not support this rule for headers with multiple values.
 * <p>
 *  The system does not distinquish between underscore and dash characters in headers. That is, it treats
-*    `example_header_name` and `example-header-name` as identical.  If two such headers appear in a request, the system
+*    {@code example_header_name} and {@code example-header-name} as identical.  If two such headers appear in a request, the system
 *    applies the action to the first header it finds. The affected header cannot be determined in advance. Oracle
 *    recommends that you do not rely on underscore or dash characters to uniquely distinguish header names.
 *
@@ -34,27 +34,27 @@ export interface ExtendHttpResponseHeaderValueRule extends model.Rule {
     /**
       * A header name that conforms to RFC 7230.
   * <p>
-  Example: `example_header_name`
+  Example: {@code example_header_name}
   *
       */
     "header": string;
     /**
       * A string to prepend to the header value. The resulting header value must still conform to RFC 7230.
   * With the following exceptions:
-  * *  value cannot contain `$`
-  * *  value cannot contain patterns like `{variable_name}`. They are reserved for future extensions. Currently, such values are invalid.
+  * *  value cannot contain {@code $}
+  * *  value cannot contain patterns like {@code {variable_name}}. They are reserved for future extensions. Currently, such values are invalid.
   * <p>
-  Example: `example_prefix_value`
+  Example: {@code example_prefix_value}
   *
       */
     "prefix"?: string;
     /**
       * A string to append to the header value. The resulting header value must still conform to RFC 7230.
   * With the following exceptions:
-  * *  value cannot contain `$`
-  * *  value cannot contain patterns like `{variable_name}`. They are reserved for future extensions. Currently, such values are invalid.
+  * *  value cannot contain {@code $}
+  * *  value cannot contain patterns like {@code {variable_name}}. They are reserved for future extensions. Currently, such values are invalid.
   * <p>
-  Example: `example_suffix_value`
+  Example: {@code example_suffix_value}
   *
       */
     "suffix"?: string;

package/lib/model/forward-to-backend-set.d.ts

@@ -21,7 +21,7 @@ export interface ForwardToBackendSet extends model.Action {
     /**
       * Name of the backend set the listener will forward the traffic to.
   * <p>
-  Example: `backendSetForImages`
+  Example: {@code backendSetForImages}
   *
       */
     "backendSetName": string;

package/lib/model/health-check-result.d.ts

@@ -26,14 +26,14 @@ export interface HealthCheckResult {
       * The IP address of the health check status report provider. This identifier helps you differentiate same-subnet
   * load balancers that report health check status.
   * <p>
-  Example: `10.0.0.7`
+  Example: {@code 10.0.0.7}
   *
       */
     "sourceIpAddress": string;
     /**
       * The date and time the data was retrieved, in the format defined by RFC3339.
   * <p>
-  Example: `2017-06-02T18:28:11+00:00`
+  Example: {@code 2017-06-02T18:28:11+00:00}
   *
       */
     "timestamp": Date;

package/lib/model/health-checker-details.d.ts

@@ -19,29 +19,29 @@ export interface HealthCheckerDetails {
     /**
       * The protocol the health check must use; either HTTP or TCP.
   * <p>
-  Example: `HTTP`
+  Example: {@code HTTP}
   *
       */
     "protocol": string;
     /**
       * The path against which to run the health check.
   * <p>
-  Example: `/healthcheck`
+  Example: {@code /healthcheck}
   *
       */
     "urlPath"?: string;
     /**
       * The backend server port against which to run the health check. If the port is not specified, the load balancer uses the
-  * port information from the `Backend` object.
+  * port information from the {@code Backend} object.
   * <p>
-  Example: `8080`
+  Example: {@code 8080}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "port"?: number;
     /**
       * The status code a healthy backend server should return.
   * <p>
-  Example: `200`
+  Example: {@code 200}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "returnCode"?: number;
@@ -49,7 +49,7 @@ export interface HealthCheckerDetails {
       * The number of retries to attempt before a backend server is considered \"unhealthy\". This number also applies
   * when recovering a server to the \"healthy\" state.
   * <p>
-  Example: `3`
+  Example: {@code 3}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "retries"?: number;
@@ -57,21 +57,21 @@ export interface HealthCheckerDetails {
       * The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply
   * returns within this timeout period.
   * <p>
-  Example: `3000`
+  Example: {@code 3000}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "timeoutInMillis"?: number;
     /**
       * The interval between health checks, in milliseconds.
   * <p>
-  Example: `10000`
+  Example: {@code 10000}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "intervalInMillis"?: number;
     /**
       * A regular expression for parsing the response body from the backend server.
   * <p>
-  Example: `^((?!false).|\\s)*$`
+  Example: {@code ^((?!false).|\\s)*$}
   *
       */
     "responseBodyRegex"?: string;
@@ -85,7 +85,7 @@ export interface HealthCheckerDetails {
   If \"false\", health checks will be done using SSL encryption if the associated backend set is configured
   * to use SSL. If the backend set is not so configured the health checks will be done using plain text.
   * <p>
-  Example: `false`
+  Example: {@code false}
   *
       */
     "isForcePlainText"?: boolean;

package/lib/model/health-checker.d.ts

@@ -21,22 +21,22 @@ export interface HealthChecker {
     /**
       * The protocol the health check must use; either HTTP or TCP.
   * <p>
-  Example: `HTTP`
+  Example: {@code HTTP}
   *
       */
     "protocol": string;
     /**
       * The path against which to run the health check.
   * <p>
-  Example: `/healthcheck`
+  Example: {@code /healthcheck}
   *
       */
     "urlPath"?: string;
     /**
       * The backend server port against which to run the health check. If the port is not specified, the load balancer uses the
-  * port information from the `Backend` object.
+  * port information from the {@code Backend} object.
   * <p>
-  Example: `8080`
+  Example: {@code 8080}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "port": number;
@@ -44,7 +44,7 @@ export interface HealthChecker {
       * The status code a healthy backend server should return. If you configure the health check policy to use the HTTP protocol,
   * you can use common HTTP status codes such as \"200\".
   * <p>
-  Example: `200`
+  Example: {@code 200}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "returnCode": number;
@@ -52,7 +52,7 @@ export interface HealthChecker {
       * The number of retries to attempt before a backend server is considered \"unhealthy\". This number also applies
   * when recovering a server to the \"healthy\" state. Defaults to 3.
   * <p>
-  Example: `3`
+  Example: {@code 3}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "retries"?: number;
@@ -60,21 +60,21 @@ export interface HealthChecker {
       * The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply
   * returns within this timeout period. Defaults to 3000 (3 seconds).
   * <p>
-  Example: `3000`
+  Example: {@code 3000}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "timeoutInMillis"?: number;
     /**
       * The interval between health checks, in milliseconds. The default is 10000 (10 seconds).
   * <p>
-  Example: `10000`
+  Example: {@code 10000}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "intervalInMillis"?: number;
     /**
       * A regular expression for parsing the response body from the backend server.
   * <p>
-  Example: `^((?!false).|\\s)*$`
+  Example: {@code ^((?!false).|\\s)*$}
   *
       */
     "responseBodyRegex": string;
@@ -88,7 +88,7 @@ export interface HealthChecker {
   If \"false\", health checks will be done using SSL encryption if the associated backend set is configured
   * to use SSL. If the backend set is not so configured the health checks will be done using plain text.
   * <p>
-  Example: `false`
+  Example: {@code false}
   *
       */
     "isForcePlainText"?: boolean;

package/lib/model/hostname-details.d.ts

@@ -19,7 +19,7 @@ export interface HostnameDetails {
     /**
       * The name of the hostname resource.
   * <p>
-  Example: `example_hostname_001`
+  Example: {@code example_hostname_001}
   *
       */
     "name": string;
@@ -27,7 +27,7 @@ export interface HostnameDetails {
       * A virtual hostname. For more information about virtual hostname string construction, see
   * [Managing Request Routing](https://docs.cloud.oracle.com/Content/Balance/Tasks/managingrequest.htm#routing).
   * <p>
-  Example: `app.example.com`
+  Example: {@code app.example.com}
   *
       */
     "hostname": string;

package/lib/model/hostname.d.ts

@@ -23,7 +23,7 @@ export interface Hostname {
       * A friendly name for the hostname resource. It must be unique and it cannot be changed. Avoid entering confidential
   * information.
   * <p>
-  Example: `example_hostname_001`
+  Example: {@code example_hostname_001}
   *
       */
     "name": string;
@@ -31,7 +31,7 @@ export interface Hostname {
       * A virtual hostname. For more information about virtual hostname string construction, see
   * [Managing Request Routing](https://docs.cloud.oracle.com/Content/Balance/Tasks/managingrequest.htm#routing).
   * <p>
-  Example: `app.example.com`
+  Example: {@code app.example.com}
   *
       */
     "hostname": string;

package/lib/model/http-header-rule.d.ts

@@ -17,7 +17,7 @@ import * as model from "../model";
  * An object that represents the advance http header options that allow the setting of http header size and allow/disallow
  * invalid characters in the http headers.
  * For example httpLargeHeaderSizeInKB=32, the http header could have 4 buffers of 32KBs each
- * This rule applies only to HTTP listeners. No more than one `HttpHeaderRule` object can be present in
+ * This rule applies only to HTTP listeners. No more than one {@code HttpHeaderRule} object can be present in
  * a given listener.
  *
  */

package/lib/model/ip-address.d.ts

@@ -20,7 +20,7 @@ export interface IpAddress {
     /**
       * An IP address.
   * <p>
-  Example: `192.168.0.3`
+  Example: {@code 192.168.0.3}
   *
       */
     "ipAddress": string;

package/lib/model/l-bcookie-session-persistence-configuration-details.d.ts

@@ -28,12 +28,12 @@ Path route rules take precedence to determine the target backend server. The loa
 * target. The system ignores invalid cookies.
 * <p>
 To disable LB cookie stickiness on a running load balancer, use the
-* {@link #updateBackendSet(UpdateBackendSetRequest) updateBackendSet} operation and specify `null` for the
-* `LBCookieSessionPersistenceConfigurationDetails` object.
+* {@link #updateBackendSet(UpdateBackendSetRequest) updateBackendSet} operation and specify {@code null} for the
+* {@code LBCookieSessionPersistenceConfigurationDetails} object.
 * <p>
-Example: `LBCookieSessionPersistenceConfigurationDetails: null`
+Example: {@code LBCookieSessionPersistenceConfigurationDetails: null}
 * <p>
-**Note:** `SessionPersistenceConfigurationDetails` (application cookie stickiness) and `LBCookieSessionPersistenceConfigurationDetails`
+**Note:** {@code SessionPersistenceConfigurationDetails} (application cookie stickiness) and {@code LBCookieSessionPersistenceConfigurationDetails}
 * (LB cookie stickiness) are mutually exclusive. An error results if you try to enable both types of session persistence.
 * <p>
 **Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.
@@ -44,7 +44,7 @@ export interface LBCookieSessionPersistenceConfigurationDetails {
       * The name of the cookie inserted by the load balancer. If this field is not configured, the cookie name defaults
   * to \"X-Oracle-BMC-LBS-Route\".
   * <p>
-  Example: `example_cookie`
+  Example: {@code example_cookie}
   * <p>
   **Notes:**
   * <p>
@@ -54,9 +54,9 @@ export interface LBCookieSessionPersistenceConfigurationDetails {
   * <p>
   *  If a backend server and the load balancer both insert cookies with the same name, the client or browser
   *    behavior can vary depending on the domain and path values associated with the cookie. If the name, domain,
-  *    and path values of the `Set-cookie` generated by a backend server and the `Set-cookie` generated by the
+  *    and path values of the {@code Set-cookie} generated by a backend server and the {@code Set-cookie} generated by the
   *    load balancer are all the same, the client or browser treats them as one cookie and returns only one of
-  *    the cookie values in subsequent requests. If both `Set-cookie` names are the same, but the domain and path
+  *    the cookie values in subsequent requests. If both {@code Set-cookie} names are the same, but the domain and path
   *    names are different, the client or browser treats them as two different cookies.
   *
       */
@@ -65,81 +65,81 @@ export interface LBCookieSessionPersistenceConfigurationDetails {
       * Whether the load balancer is prevented from directing traffic from a persistent session client to
   * a different backend server if the original server is unavailable. Defaults to false.
   * <p>
-  Example: `false`
+  Example: {@code false}
   *
       */
     "disableFallback"?: boolean;
     /**
-      * The domain in which the cookie is valid. The `Set-cookie` header inserted by the load balancer contains a
+      * The domain in which the cookie is valid. The {@code Set-cookie} header inserted by the load balancer contains a
   * domain attribute with the specified value.
   * <p>
   This attribute has no default value. If you do not specify a value, the load balancer does not insert the domain
-  * attribute into the `Set-cookie` header.
+  * attribute into the {@code Set-cookie} header.
   * <p>
   **Notes:**
   * <p>
   *  [RFC 6265 - HTTP State Management Mechanism](https://www.ietf.org/rfc/rfc6265.txt) describes client and
-  *    browser behavior when the domain attribute is present or not present in the `Set-cookie` header.
+  *    browser behavior when the domain attribute is present or not present in the {@code Set-cookie} header.
   * <p>
-     If the value of the `Domain` attribute is `example.com` in the `Set-cookie` header, the client includes
-  *    the same cookie in the `Cookie` header when making HTTP requests to `example.com`, `www.example.com`, and
-  *    `www.abc.example.com`. If the `Domain` attribute is not present, the client returns the cookie only for
+     If the value of the {@code Domain} attribute is {@code example.com} in the {@code Set-cookie} header, the client includes
+  *    the same cookie in the {@code Cookie} header when making HTTP requests to {@code example.com}, {@code www.example.com}, and
+  *    {@code www.abc.example.com}. If the {@code Domain} attribute is not present, the client returns the cookie only for
   *    the domain to which the original request was made.
   * <p>
-  *  Ensure that this attribute specifies the correct domain value. If the `Domain` attribute in the `Set-cookie`
+  *  Ensure that this attribute specifies the correct domain value. If the {@code Domain} attribute in the {@code Set-cookie}
   *    header does not include the domain to which the original request was made, the client or browser might reject
-  *    the cookie. As specified in RFC 6265, the client accepts a cookie with the `Domain` attribute value `example.com`
-  *    or `www.example.com` sent from `www.example.com`. It does not accept a cookie with the `Domain` attribute
-  *    `abc.example.com` or `www.abc.example.com` sent from `www.example.com`.
+  *    the cookie. As specified in RFC 6265, the client accepts a cookie with the {@code Domain} attribute value {@code example.com}
+  *    or {@code www.example.com} sent from {@code www.example.com}. It does not accept a cookie with the {@code Domain} attribute
+  *    {@code abc.example.com} or {@code www.abc.example.com} sent from {@code www.example.com}.
   * <p>
-  Example: `example.com`
+  Example: {@code example.com}
   *
       */
     "domain"?: string;
     /**
-      * The path in which the cookie is valid. The `Set-cookie header` inserted by the load balancer contains a `Path`
+      * The path in which the cookie is valid. The {@code Set-cookie header} inserted by the load balancer contains a {@code Path}
   * attribute with the specified value.
   * <p>
   Clients include the cookie in an HTTP request only if the path portion of the request-uri matches, or is a
-  * subdirectory of, the cookie's `Path` attribute.
+  * subdirectory of, the cookie's {@code Path} attribute.
   * <p>
-  The default value is `/`.
+  The default value is {@code /}.
   * <p>
-  Example: `/example`
+  Example: {@code /example}
   *
       */
     "path"?: string;
     /**
-      * The amount of time the cookie remains valid. The `Set-cookie` header inserted by the load balancer contains
-  * a `Max-Age` attribute with the specified value.
+      * The amount of time the cookie remains valid. The {@code Set-cookie} header inserted by the load balancer contains
+  * a {@code Max-Age} attribute with the specified value.
   * <p>
   The specified value must be at least one second. There is no default value for this attribute. If you do not
-  * specify a value, the load balancer does not include the `Max-Age` attribute in the `Set-cookie` header. In
+  * specify a value, the load balancer does not include the {@code Max-Age} attribute in the {@code Set-cookie} header. In
   * most cases, the client or browser retains the cookie until the current session ends, as defined by the client.
   * <p>
-  Example: `3600`
+  Example: {@code 3600}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "maxAgeInSeconds"?: number;
     /**
-      * Whether the `Set-cookie` header should contain the `Secure` attribute. If `true`, the `Set-cookie` header
-  * inserted by the load balancer contains the `Secure` attribute, which directs the client or browser to send the
+      * Whether the {@code Set-cookie} header should contain the {@code Secure} attribute. If {@code true}, the {@code Set-cookie} header
+  * inserted by the load balancer contains the {@code Secure} attribute, which directs the client or browser to send the
   * cookie only using a secure protocol.
   * <p>
-  **Note:** If you set this field to `true`, you cannot associate the corresponding backend set with an HTTP
+  **Note:** If you set this field to {@code true}, you cannot associate the corresponding backend set with an HTTP
   * listener.
   * <p>
-  Example: `true`
+  Example: {@code true}
   *
       */
     "isSecure"?: boolean;
     /**
-      * Whether the `Set-cookie` header should contain the `HttpOnly` attribute. If `true`, the `Set-cookie` header
-  * inserted by the load balancer contains the `HttpOnly` attribute, which limits the scope of the cookie to HTTP
+      * Whether the {@code Set-cookie} header should contain the {@code HttpOnly} attribute. If {@code true}, the {@code Set-cookie} header
+  * inserted by the load balancer contains the {@code HttpOnly} attribute, which limits the scope of the cookie to HTTP
   * requests. This attribute directs the client or browser to omit the cookie when providing access to cookies
   * through non-HTTP APIs. For example, it restricts the cookie from JavaScript channels.
   * <p>
-  Example: `true`
+  Example: {@code true}
   *
       */
     "isHttpOnly"?: boolean;

package/lib/model/listener-details.d.ts

@@ -20,14 +20,14 @@ export interface ListenerDetails {
     /**
       * The name of the associated backend set.
   * <p>
-  Example: `example_backend_set`
+  Example: {@code example_backend_set}
   *
       */
     "defaultBackendSetName": string;
     /**
       * The communication port for the listener.
   * <p>
-  Example: `80`
+  Example: {@code 80}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "port": number;
@@ -36,7 +36,7 @@ export interface ListenerDetails {
   * To get a list of valid protocols, use the {@link #listProtocols(ListProtocolsRequest) listProtocols}
   * operation.
   * <p>
-  Example: `HTTP`
+  Example: {@code HTTP}
   *
       */
     "protocol": string;
@@ -45,12 +45,12 @@ export interface ListenerDetails {
      */
     "hostnameNames"?: Array<string>;
     /**
-      * Deprecated. Please use `routingPolicies` instead.
+      * Deprecated. Please use {@code routingPolicies} instead.
   * <p>
   The name of the set of path-based routing rules, {@link PathRouteSet},
   * applied to this listener's traffic.
   * <p>
-  Example: `example_path_route_set`
+  Example: {@code example_path_route_set}
   *
       */
     "pathRouteSetName"?: string;
@@ -59,7 +59,7 @@ export interface ListenerDetails {
     /**
       * The name of the routing policy applied to this listener's traffic.
   * <p>
-  Example: `example_routing_policy`
+  Example: {@code example_routing_policy}
   *
       */
     "routingPolicyName"?: string;

package/lib/model/listener.d.ts

@@ -23,21 +23,21 @@ export interface Listener {
     /**
       * A friendly name for the listener. It must be unique and it cannot be changed.
   * <p>
-  Example: `example_listener`
+  Example: {@code example_listener}
   *
       */
     "name": string;
     /**
       * The name of the associated backend set.
   * <p>
-  Example: `example_backend_set`
+  Example: {@code example_backend_set}
   *
       */
     "defaultBackendSetName": string;
     /**
       * The communication port for the listener.
   * <p>
-  Example: `80`
+  Example: {@code 80}
   *  Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
       */
     "port": number;
@@ -46,7 +46,7 @@ export interface Listener {
   * To get a list of valid protocols, use the {@link #listProtocols(ListProtocolsRequest) listProtocols}
   * operation.
   * <p>
-  Example: `HTTP`
+  Example: {@code HTTP}
   *
       */
     "protocol": string;
@@ -55,12 +55,12 @@ export interface Listener {
      */
     "hostnameNames"?: Array<string>;
     /**
-      * Deprecated. Please use `routingPolicies` instead.
+      * Deprecated. Please use {@code routingPolicies} instead.
   * <p>
   The name of the set of path-based routing rules, {@link PathRouteSet},
   * applied to this listener's traffic.
   * <p>
-  Example: `example_path_route_set`
+  Example: {@code example_path_route_set}
   *
       */
     "pathRouteSetName"?: string;
@@ -76,7 +76,7 @@ export interface Listener {
     /**
       * The name of the routing policy applied to this listener's traffic.
   * <p>
-  Example: `example_routing_policy_name`
+  Example: {@code example_routing_policy_name}
   *
       */
     "routingPolicyName"?: string;

package/lib/model/load-balancer-health-summary.d.ts

@@ -24,21 +24,21 @@ export interface LoadBalancerHealthSummary {
     /**
      * The overall health status of the load balancer.
      * <p>
-     *  **OK:** All backend sets associated with the load balancer return a status of `OK`.
+     *  **OK:** All backend sets associated with the load balancer return a status of {@code OK}.
      * <p>
-     *  **WARNING:** At least one of the backend sets associated with the load balancer returns a status of `WARNING`,
-     * no backend sets return a status of `CRITICAL`, and the load balancer life cycle state is `ACTIVE`.
+     *  **WARNING:** At least one of the backend sets associated with the load balancer returns a status of {@code WARNING},
+     * no backend sets return a status of {@code CRITICAL}, and the load balancer life cycle state is {@code ACTIVE}.
      * <p>
-     *  **CRITICAL:** One or more of the backend sets associated with the load balancer return a status of `CRITICAL`.
+     *  **CRITICAL:** One or more of the backend sets associated with the load balancer return a status of {@code CRITICAL}.
      * <p>
      *  **UNKNOWN:** If any one of the following conditions is true:
      * <p>
-     *  The load balancer life cycle state is not `ACTIVE`.
+     *  The load balancer life cycle state is not {@code ACTIVE}.
      * <p>
      *  No backend sets are defined for the load balancer.
      * <p>
-     *  More than half of the backend sets associated with the load balancer return a status of `UNKNOWN`, none of the backend
-     *        sets return a status of `WARNING` or `CRITICAL`, and the load balancer life cycle state is `ACTIVE`.
+     *  More than half of the backend sets associated with the load balancer return a status of {@code UNKNOWN}, none of the backend
+     *        sets return a status of {@code WARNING} or {@code CRITICAL}, and the load balancer life cycle state is {@code ACTIVE}.
      * <p>
      *  The system could not retrieve metrics for any reason.
      *