diff --git a/06_lightning_architecture.asciidoc b/06_lightning_architecture.asciidoc
index c21dd1b..3c59dd5 100644
--- a/06_lightning_architecture.asciidoc
+++ b/06_lightning_architecture.asciidoc
@@ -44,7 +44,7 @@ pass:[<a data-type="xref" href="#onion_routing" data-xrefstyle="chap-num-title">
 
 pass:[<a data-type="xref" href="#gossip" data-xrefstyle="chap-num-title">#gossip</a>]:: In this chapter we will look at how Lightning nodes find each other and learn about published channels to construct a channel graph that they can use to find paths across the network.
 
-pass:[<a data-type="xref" href="#path_finding" data-xrefstyle="chap-num-title">>#path_finding</a>]:: Next, we will see how the information from the gossip protocol is used by each node to build a "map" of the entire network, which it can use to find paths from one point to another to route payments. We'll also look at the exiting innovations in pathfinding, such as multipart payments.
+pass:[<a data-type="xref" href="#path_finding" data-xrefstyle="chap-num-title">#path_finding</a>]:: Next, we will see how the information from the gossip protocol is used by each node to build a "map" of the entire network, which it can use to find paths from one point to another to route payments. We'll also look at the exiting innovations in pathfinding, such as multipart payments.
 
 pass:[<a data-type="xref" href="#wire_protocol" data-xrefstyle="chap-num-title">#wire_protocol</a>]:: Underpinning the Lightning Network is the peer-to-peer protocol that nodes use to exchange messages about the network and about their channels. In this chapter we look at how those messages are constructed and the extension capabilities built into messages with feature bits and Type-Length-Value (TLV) encoding.