But, in reality, it is the display server process that offers display services to client programs that use them.
I can't really see a solid line of differentiation between an 'X server' and a browser. Would you call the browser an HTML/Javascript server?
X Windows is using computer science jargon instead, where "client" and "server" are words that describe roles that two programs might play in a specific kind of relationship with each other.
How dare you insinuate that I might be a system administrator. Or that system administrators really don't know much beyond their domain. I won't stand for it!
I'm sure 'X windows' is technically a server in some the strictest sense. Technically I guess the client app issues a request for user input which is served by the X server. To extend that model the X server issues a sub-request to the user who fulfils that request. To me this seems to twist the terminology to the point where the user is just another service available to the program. It reflects a view of reality that does not appeal to ordinary end users and I believe this limited the success of X windows and unix/linux on the desktop.
X display servers (which we both agree are local) do not initiate clients to display on them, end users do this work - you can see this quite easily by initiating a client when you don't have an X display - the app will look for a $DISPLAY variable and attempt to connect to that display. The app is launched first by the user, and connects to the display server.
Commercially speaking, X11 was a great success. It is the de facto windowing system for UNIX and UNIX-like systems despite all of the horrors it brings.
And if you believe Windows is the most popular OS family, then being the defacto windowing system for the second most popular OS family is still a great success.
I just hope that we get the words "client" and "server" defined correctly this time around.