What JorgeM says, plus this: Explanation of TCP/IP takes BOOKS, not just chapters of same... I have several linear feet of books on my shelf that are all required to really understand the protocols. I should know, since in the past I have implemented an entire TCP/IP stack for a real-time operating system from the DDN Protocol handbooks (a foot of that shelf space) which define the underpinnings of TCP/IP. Other books (such as Comer and Stevens) get into socket programming and such.
TCP/IP is short form of Transmission Control Protocol and Internet Protocol.
IP - is responsible for moving packet of data from node to node. IP forwards each packet based on a four byte destination address (the IP number). The Internet authorities assign ranges of numbers to different organizations. The organizations assign groups of their numbers to departments. IP operates on gateway machines that move data from department to organization to region and then around the world.
TCP - is responsible for verifying the correct delivery of data from client to server. Data can be lost in the intermediate network. TCP adds support to detect errors or lost data and to trigger retransmission until the data is correctly and completely received.