Apply suggestions from code review

Co-authored-by: Rob Scott <rob.scott87@gmail.com>

Author: 08volt

site-src/api-types/backendtlspolicy.md

@@ -124,13 +124,21 @@ Also note:
     - Wildcard hostnames are not allowed.
 
 #### Subject Alternative Names
+
+??? example "Experimental Channel since v1.2.0"
+
+    This field was added to BackendTLSPolicy in `v1.2.0`
 The subjectAltNames field enables separation between the SNI (specified by hostname) and certificate identity validation. When specified, the certificate served by the backend must have at least one Subject Alternative Name matching one of the specified values. This is particularly useful for SPIFFE implementations where URI-based SANs may not be valid SNIs.
 Subject Alternative Names can be of two types:
 
 - Hostname: DNS name format
 - URI: URI format (e.g., SPIFFE ID)
 
 #### TLS Options
+
+??? example "Experimental Channel since v1.2.0"
+
+    This field was added to BackendTLSPolicy in `v1.2.0`
 The options field allows specification of implementation-specific TLS configurations, similar to the TLS options field on Gateway Listeners. This can include:
 
 - Vendor-specific mTLS automation configuration