Fix hierarchy of headers on docs landing page

This commit is contained in:
thunderbiscuit 2022-02-24 10:48:47 -05:00
parent b23a0747b5
commit 364ad95e85
No known key found for this signature in database
GPG Key ID: 88253696EB836462

View File

@ -46,12 +46,13 @@
//! ```toml //! ```toml
//! bdk = "0.16.1" //! bdk = "0.16.1"
//! ``` //! ```
//!
//! # Examples
#![cfg_attr( #![cfg_attr(
feature = "electrum", feature = "electrum",
doc = r##" doc = r##"
## Sync the balance of a descriptor ## Sync the balance of a descriptor
### Example
```no_run ```no_run
use bdk::Wallet; use bdk::Wallet;
use bdk::database::MemoryDatabase; use bdk::database::MemoryDatabase;
@ -80,7 +81,6 @@ fn main() -> Result<(), bdk::Error> {
//! //!
//! ## Generate a few addresses //! ## Generate a few addresses
//! //!
//! ### Example
//! ``` //! ```
//! use bdk::{Wallet}; //! use bdk::{Wallet};
//! use bdk::database::MemoryDatabase; //! use bdk::database::MemoryDatabase;
@ -106,7 +106,6 @@ fn main() -> Result<(), bdk::Error> {
doc = r##" doc = r##"
## Create a transaction ## Create a transaction
### Example
```no_run ```no_run
use bdk::{FeeRate, Wallet}; use bdk::{FeeRate, Wallet};
use bdk::database::MemoryDatabase; use bdk::database::MemoryDatabase;
@ -150,7 +149,6 @@ fn main() -> Result<(), bdk::Error> {
//! //!
//! ## Sign a transaction //! ## Sign a transaction
//! //!
//! ### Example
//! ```no_run //! ```no_run
//! use std::str::FromStr; //! use std::str::FromStr;
//! //!
@ -192,7 +190,7 @@ fn main() -> Result<(), bdk::Error> {
//! * `async-interface`: async functions in bdk traits //! * `async-interface`: async functions in bdk traits
//! * `keys-bip39`: [BIP-39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki) mnemonic codes for generating deterministic keys //! * `keys-bip39`: [BIP-39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki) mnemonic codes for generating deterministic keys
//! //!
//! ## Internal features //! # Internal features
//! //!
//! These features do not expose any new API, but influence internal implementation aspects of //! These features do not expose any new API, but influence internal implementation aspects of
//! BDK. //! BDK.