TLS docs for tokio-postgres

Author: sfackler

postgres/src/lib.rs

@@ -50,7 +50,7 @@
 //!
 //! TLS support is implemented via external libraries. `Client::connect` and `Config::connect` take a TLS implementation
 //! as an argument. The `NoTls` type in this crate can be used when TLS is not required. Otherwise, the
-//! `tokio-postgres-openssl` and `tokio-postgres-native-tls` crates provide implementations backed by the `postgres` and
+//! `tokio-postgres-openssl` and `tokio-postgres-native-tls` crates provide implementations backed by the `openssl` and
 //! `native-tls` crates, respectively.
 #![warn(clippy::all, rust_2018_idioms, missing_docs)]
 

tokio-postgres/src/lib.rs

@@ -101,6 +101,13 @@
 //! The client works with arbitrary `AsyncRead + AsyncWrite` streams. Convenience APIs are provided to handle the
 //! connection process, but these are gated by the `runtime` Cargo feature, which is enabled by default. If disabled,
 //! all dependence on the tokio runtime is removed.
+//!
+//! # SSL/TLS support
+//!
+//! TLS support is implemented via external libraries. `Client::connect` and `Config::connect` take a TLS implementation
+//! as an argument. The `NoTls` type in this crate can be used when TLS is not required. Otherwise, the
+//! `tokio-postgres-openssl` and `tokio-postgres-native-tls` crates provide implementations backed by the `openssl` and
+//! `native-tls` crates, respectively.
 #![doc(html_root_url = "https://docs.rs/tokio-postgres/0.4.0-rc.1")]
 #![warn(rust_2018_idioms, clippy::all, missing_docs)]