docs(config): fix Peering header
Peering is top level namespace
Marcin Rataj committed
Aug 25, 2020 at 13:42 UTC
135b90e08713c13de5adb7de949ab0d6354736a6
1 file changed
+4
-4
docs/config.md
+4
-4
@@ -179,8 +179,8 @@ does (e.g, `"1d2h4m40.01s"`).
179
- [`Pubsub`](#pubsub)
180
- [`Pubsub.Router`](#pubsubrouter)
181
- [`Pubsub.DisableSigning`](#pubsubdisablesigning)
182
- - [`Peering`](#peering)
183
- - [`Peering.Peers`](#peeringpeers)
182
+- [`Peering`](#peering)
183
+ - [`Peering.Peers`](#peeringpeers)
184
- [`Reprovider`](#reprovider)
185
- [`Reprovider.Interval`](#reproviderinterval)
186
- [`Reprovider.Strategy`](#reproviderstrategy)
@@ -846,7 +846,7 @@ Default: `false`
846
847
Type: `bool`
848
849
-### `Peering`
849
+## `Peering`
850
851
Configures the peering subsystem. The peering subsystem configures go-ipfs to
852
connect to, remain connected to, and reconnect to a set of nodes. Nodes should
@@ -883,7 +883,7 @@ Peering can be asymmetric or symmetric:
883
connection may flap repeatedly. Be careful when asymmetrically peering to not
884
overload peers.
885
886
-#### `Peering.Peers`
886
+### `Peering.Peers`
887
888
The set of peers with which to peer.
889