why oh why must authors do this.

I hate it when authors will assume their book is going to read by neophytes so they better include a detailed description of what html is - or what a browser is....

Anyone reading this book is probably looking to design enterprise quality web applications using UML. One would think that based on the title at least...Which is a fairly advanced goal. How would anyone who requires UML exposure not understand a client-server relationship???
This author wastes time and paper droning on about ridiculously obvious topics. Let me give you an example:::

"HTML defines a set of tags that can be used either to tell the browser how to render something or to define a link to another Web page. All tags are enclosed by angled brackets (< and >). Tags are usually used in pairs, with beginning and ending tags. For example, the emphasis tag: italicizes a word. A sample sentence and the HTML to render it follow:"

WOW!!!! How very relevant!!!!
Anyway he's not the first author to increase the book's shipping weight w/ fluff and he probably wont be the last.