Fixup some things with the updated website

docs/features/https.md

@@ -15,7 +15,7 @@ Specific security vs. connectivity decisions are implemented by [ConnectionSpec]
  * `COMPATIBLE_TLS` is a secure configuration that connects to secure–but not current–HTTPS servers.
  * `CLEARTEXT` is an insecure configuration that is used for `http://` URLs.
 
-These loosely follow the model set in [Google Cloud Policies](https://cloud.google.com/load-balancing/docs/ssl-policies-concepts). We [track changes](../changelogs/tls_configuration_history.md) to this policy.
+These loosely follow the model set in [Google Cloud Policies](https://cloud.google.com/load-balancing/docs/ssl-policies-concepts). We [track changes](tls_configuration_history.md) to this policy.
 
 By default, OkHttp will attempt a `MODERN_TLS` connection.  However by configuring the client connectionSpecs you can allow a fall back to `COMPATIBLE_TLS` connection if the modern configuration fails.
 
@@ -52,19 +52,19 @@ common cipher suite and TLS version, your call will fail like this:
 ```
 Caused by: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0x7f2719a89e80:
     Failure in SSL library, usually a protocol error
-        error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake 
+        error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake
         failure (external/openssl/ssl/s23_clnt.c:770 0x7f2728a53ea0:0x00000000)
     at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
 ```
 
 You can check a web server's configuration using [Qualys SSL Labs][qualys]. OkHttp's TLS
-configuration history is [tracked here](../changelogs/tls_configuration_history.md).
+configuration history is [tracked here](tls_configuration_history.md).
 
 Applications expected to be installed on older Android devices should consider adopting the
 [Google Play Services’ ProviderInstaller][provider_installer]. This will increase security for users
 and increase connectivity with web servers.
 
-### Certificate Pinning ([.kt][CertificatePinningKotlin], [.java][CertificatePinningJava]) 
+### Certificate Pinning ([.kt][CertificatePinningKotlin], [.java][CertificatePinningJava])
 
 By default, OkHttp trusts the certificate authorities of the host platform. This strategy maximizes connectivity, but it is subject to certificate authority attacks such as the [2011 DigiNotar attack](https://www.computerworld.com/article/2510951/cybercrime-hacking/hackers-spied-on-300-000-iranians-using-fake-google-certificate.html). It also assumes your HTTPS servers’ certificates are signed by a certificate authority.
 
@@ -78,15 +78,15 @@ Use [CertificatePinner](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-cert
                   .add("publicobject.com", "sha256/afwiKY3RxoMmLkuRW1l7QsPZTJPwDS2pdDROQjXw8ig=")
                   .build())
           .build()
-    
+
       fun run() {
         val request = Request.Builder()
             .url("https://publicobject.com/robots.txt")
             .build()
-    
+
         client.newCall(request).execute().use { response ->
           if (!response.isSuccessful) throw IOException("Unexpected code $response")
-    
+
           for (certificate in response.handshake!!.peerCertificates) {
             println(CertificatePinner.pin(certificate))
           }
@@ -101,15 +101,15 @@ Use [CertificatePinner](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-cert
                   .add("publicobject.com", "sha256/afwiKY3RxoMmLkuRW1l7QsPZTJPwDS2pdDROQjXw8ig=")
                   .build())
           .build();
-    
+
       public void run() throws Exception {
         Request request = new Request.Builder()
             .url("https://publicobject.com/robots.txt")
             .build();
-    
+
         try (Response response = client.newCall(request).execute()) {
           if (!response.isSuccessful()) throw new IOException("Unexpected code " + response);
-    
+
           for (Certificate certificate : response.handshake().peerCertificates()) {
             System.out.println(CertificatePinner.pin(certificate));
           }
@@ -124,34 +124,34 @@ The full code sample shows how to replace the host platform’s certificate auth
 === ":material-language-kotlin: Kotlin"
     ```kotlin
       private val client: OkHttpClient
-    
+
       init {
         val trustManager = trustManagerForCertificates(trustedCertificatesInputStream())
         val sslContext = SSLContext.getInstance("TLS")
         sslContext.init(null, arrayOf<TrustManager>(trustManager), null)
         val sslSocketFactory = sslContext.socketFactory
-    
+
         client = OkHttpClient.Builder()
             .sslSocketFactory(sslSocketFactory, trustManager)
             .build()
       }
-    
+
       fun run() {
         val request = Request.Builder()
             .url("https://publicobject.com/helloworld.txt")
             .build()
-    
+
         client.newCall(request).execute().use { response ->
           if (!response.isSuccessful) throw IOException("Unexpected code $response")
-    
+
           for ((name, value) in response.headers) {
             println("$name: $value")
           }
-    
+
           println(response.body!!.string())
         }
       }
-    
+
       /**
        * Returns an input stream containing one or more certificate PEM files. This implementation just
        * embeds the PEM files in Java strings; most applications will instead read this from a resource
@@ -160,7 +160,7 @@ The full code sample shows how to replace the host platform’s certificate auth
       private fun trustedCertificatesInputStream(): InputStream {
         ... // Full source omitted. See sample.
       }
-    
+
       private fun trustManagerForCertificates(inputStream: InputStream): X509TrustManager {
         ... // Full source omitted. See sample.
       }
@@ -168,7 +168,7 @@ The full code sample shows how to replace the host platform’s certificate auth
 === ":material-language-java: Java"
     ```java
       private final OkHttpClient client;
-    
+
       public CustomTrust() {
         X509TrustManager trustManager;
         SSLSocketFactory sslSocketFactory;
@@ -180,25 +180,25 @@ The full code sample shows how to replace the host platform’s certificate auth
         } catch (GeneralSecurityException e) {
           throw new RuntimeException(e);
         }
-    
+
         client = new OkHttpClient.Builder()
             .sslSocketFactory(sslSocketFactory, trustManager)
             .build();
       }
-    
+
       public void run() throws Exception {
         Request request = new Request.Builder()
             .url("https://publicobject.com/helloworld.txt")
             .build();
-    
+
         Response response = client.newCall(request).execute();
         System.out.println(response.body().string());
       }
-    
+
       private InputStream trustedCertificatesInputStream() {
         ... // Full source omitted. See sample.
       }
-    
+
       public SSLContext sslContextForTrustedCertificates(InputStream in) {
         ... // Full source omitted. See sample.
       }