No Builder::native_tls with default features

Since the function "doesn't exist", we can't link to it. Arguably, the
docs should only be tested with all features enabled, but for now just
don't try to link to `native_tls`.

rust-runtime/smithy-client/src/hyper_impls.rs

@@ -61,7 +61,7 @@ where
     /// For convenience, this constructor type-erases the concrete TLS connector backend used using
     /// dynamic dispatch. This comes at a slight runtime performance cost. See
     /// [`DynConnector`](crate::erase::DynConnector) for details. To avoid that overhead, use
-    /// [`Builder::rustls`] or [`Builder::native_tls`] instead.
+    /// [`Builder::rustls`] or `Builder::native_tls` instead.
     pub fn https() -> Self {
         #[cfg(feature = "rustls")]
         let with_https = |b: Builder<_>| b.rustls();
@@ -91,7 +91,7 @@ impl<M, R> Builder<(), M, R> {
     /// Connect to the service over HTTPS using Rustls.
     ///
     /// This is exactly equivalent to [`Builder::rustls`]. If you instead wish to use `native_tls`,
-    /// use [`Builder::native_tls`].
+    /// use `Builder::native_tls`.
     pub fn https(
         self,
     ) -> Builder<HyperAdapter<hyper_rustls::HttpsConnector<hyper::client::HttpConnector>>, M, R>

rust-runtime/smithy-client/src/lib.rs

@@ -79,7 +79,7 @@ type BoxError = Box<dyn Error + Send + Sync>;
 /// With the `hyper` feature enabled, you can construct a `Client` directly from a
 /// [`hyper::Client`] using [`Builder::hyper`]. You can also enable the `rustls` or `native-tls`
 /// features to construct a Client against a standard HTTPS endpoint using [`Builder::rustls`] and
-/// [`Builder::native_tls`] respectively.
+/// `Builder::native_tls` respectively.
 #[derive(Debug)]
 pub struct Client<
     Connector = erase::DynConnector,