diff --git a/src/api/auth/scram.rs b/src/api/auth/scram.rs
index 0d19eb5..1903af1 100644
--- a/src/api/auth/scram.rs
+++ b/src/api/auth/scram.rs
@@ -459,7 +459,7 @@ fn xor(lhs: &[u8], rhs: &[u8]) -> Vec<u8> {
 /// 1. use sha-256 if the certificate's algorithm is md5 or sha-1
 /// 2. use the certificate's algorithm if it's neither md5 or sha-1
 /// 3. if the certificate has 0 or more than 1 signature algorithm, the
-/// behaviour is undefined at the time.
+///    behaviour is undefined at the time.
 fn compute_cert_signature(cert: &[u8]) -> PgWireResult<Vec<u8>> {
     let certs = CapturedX509Certificate::from_pem_multiple(cert)
         .map_err(|e| PgWireError::ApiError(Box::new(e)))?;
diff --git a/src/lib.rs b/src/lib.rs
index 4963d89..26b38bd 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -13,10 +13,10 @@
 //!
 //! - Startup: client-server handshake and authentication.
 //! - Simple Query: The legacy query protocol of postgresql. Query are provided
-//! as string, and server is allowed to stream data in response.
+//!   as string, and server is allowed to stream data in response.
 //! - Extended Query: A new sub-protocol for query which has ability to cache
-//! the query on server-side and reuse it with new parameters. The response part
-//! is identical to Simple Query.
+//!   the query on server-side and reuse it with new parameters. The response part
+//!   is identical to Simple Query.
 //!
 //! Also note that Postgres Wire Protocol has no semantics about SQL, so
 //! literally you can use any query language, data formats or even natural
@@ -37,7 +37,7 @@
 //! application from any level of abstraction. They are:
 //!
 //! - Protocol layer: Just use message definitions and codecs in `messages`
-//! module.
+//!   module.
 //! - Message handler layer: Implement `on_` prefixed methods in traits:
 //!   - `StartupHandler`
 //!   - `SimpleQueryHandler`
@@ -50,9 +50,9 @@
 //! ## Features
 //!
 //! - `server-api-aws-lc-rs` is enabled by default, it includes all three layers
-//! of our API and uses `aws-lc-rs` as crypto backend.
+//!   of our API and uses `aws-lc-rs` as crypto backend.
 //! - `server-api-ring` is almost same to `server-api-aws-lc-rs` except for it's
-//! using `ring` as crypto backend.
+//!   using `ring` as crypto backend.
 //! - `scram` for the SASL/SCRAM authenticator.
 //! - Turn off default features if you just use our Protocol layer.
 //!