Update onion-routing-htlc-forwarding.asciidoc

onion-routing-htlc-forwarding.asciidoc

@@ -61,6 +61,6 @@ We see this example as spiritually similar to the chain analysis already perform
 Fixing the packet size solves the problem of routing nodes knowing how far a packet is along the route.
 Whenever a routing node peels off a layer, it adds another layer of junk data to the end, restoring the packet to its "full" size.
 In this way, even if a packet has already been transmitted 18 hops, the 19th routing node would still see that the packet contains enough data for up to 20 hops.
-It would have no way of determining if it was the first routing node or the second last routing node.
+The packet size would not provide useful information to the 19th routing node for it to determine if it was the first routing node or the second last routing node.
 If it is not the recipient itself, then it knows only that the recipient is someone it is connected to by up to 20 hops.
 Assuming a sufficiently complex network with a large number of nodes, the size of the packet then gives them no useful information about the source or the destination of the payment.