Typo in Transport Concept Docs- regular addressing of TCP port doesn't match multiaddr TCP port

[tesla809]

Found a small typo in the Transport docs in the Concepts section.

In the section explaining multiaddresses, shouldn't the TCP ending of the multiaddress: /ip4/7.7.7.7/tcp/6543 match the more familiar construction 7.7.7.7:6542?

7.7.7.7:6542 =? /ip4/7.7.7.7/tcp/6543

Here’s an example of a multiaddr for a TCP/IP transport:

/ip4/7.7.7.7/tcp/6543
This is equivalent to the more familiar 7.7.7.7:6542 construction, but it has the advantage of being explicit about the protocols that are being described. With the multiaddr, you can see at a glance that the 7.7.7.7 address belongs to the IPv4 protocol, and the 6543 belongs to TCP.

[p-shahi]

Addressed by #146