Prevent mixup for new programmers
Prevent mixup for new programmers

The documentation, inadvertently, causes confusion for newer programmers, hindering their learning curve and ability to learn `socket.io` faster.

This proposed change aims at preventing this confusion to allow new programmers easier access to resources, especially when searching the web for more information.

The name `socket` in the documentation refers to the API gateway, or abstraction layer, related to the `client` and other properties. However, in the rest of the programming world, `sockets` usually refer to Berklee sockets or the lower-level communication channel that is used to implement Protocols such as the Websocket Protocol and HTTP.

New programmers often search for more informations using the `sockets` keyword when they are grappling with learning the `socket.io` API.

A good example is the stack overflow site, where newer programmers incorrectly tag their questions `sockets` and in turn don't get a fast response to their questions.

By simply changing the name of the variable used to describe socket.io's "Socket" class instances from `socket` to `client`, this mixup should be mitigated considerably.
Automattic/socket.io,mosoft521/socket.io,mosoft521/socket.io,Automattic/socket.io,Nibbler999/socket.io,CxRes/socket.io,chapuzzo/socket.io,SimenB/socket.io,DanCard0/ionic-chat-server,socketio/socket.io,l3dlp/socket.io,socketio/socket.io,l3dlp/socket.io,jondubois/socket.io