Skip to content

Commit 5662ef9

Browse files
committed
Tweaked disclaimer and/or book descriptions
Signed-off-by: Jens Oliver Meiert <[email protected]>
1 parent 92b507f commit 5662ef9

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

manuscript/author.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Available at [Amazon](https://www.amazon.com/dp/B0B4SD84B2/?tag=meiert-20), [App
1919

2020
## [_On Web Development_](https://meiert.com/en/blog/on-web-development/) (2015)
2121

22-
> _On Web Development_ bundles 134 articles and the last 11 years of technical writings by Jens Oliver Meiert (meiert.com). Freshly reordered and commented, the articles cover processes and maintenance, HTML and CSS, standards, as well as development and design in general; they range from coding basics and principles, to carefully scathing criticism, to tips and tricks and trivia.
22+
> _On Web Development_ bundles 134 articles and the last 11 years of technical writings by Jens Oliver Meiert (meiert.com). Freshly reordered and commented, the articles cover processes and maintenance, HTML and CSS, standards, as well as development and design in general; they include coding basics and principles, carefully scathing criticism, and tips and tricks and trivia.
2323
2424
Available at [Amazon](https://www.amazon.com/dp/B010PQPT90/?tag=meiert-20).
2525

manuscript/book.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,10 @@ Published by [Frontend Dogma](https://frontenddogma.com/), c/o Jens Oliver Meier
88
Editor: Kirsty MacRae
99
Reviewer: Tony Ruscoe
1010

11-
While author and publisher have used good faith efforts to ensure that the information contained in this book is accurate, they disclaim responsibility for errors or omissions, including, without limitation, responsibility for damages resulting from the use of or reliance on this book. Use of the information contained in this book is at your own risk. If code or technology this book contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with the respective licenses and rights.
11+
While author and publisher have used good faith efforts to ensure that the information in this book is accurate, they disclaim responsibility for errors or omissions, including, without limitation, responsibility for damages resulting from the use of or reliance on this book. Use of the information in this book is at your own risk. If code or technology this book contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with the respective licenses and rights.
1212

1313
Contact +1-754-400-0999 or [email protected] for more information.
1414

1515
Follow [Frontend Dogma on Mastodon](https://mas.to/@frontenddogma).
1616

17-
[1.4.28]
17+
[1.4.29]

manuscript/operation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Operational Optimization
22

3-
In this section, we’re going to talk about our options for writing higher quality CSS while we’re right at it, during development and in operation. This type of optimization benefits us as developers. (The next section will deal with options to optimize for production, that is, for release and live use, and for the benefit of our users.)
3+
In this section, we’re going to talk about our options for writing higher-quality CSS while we’re right at it, during development and in operation. This type of optimization benefits us as developers. (The next section will deal with options to optimize for production, that is, for release and live use, and for the benefit of our users.)
44

55
To get a better look at CSS itself, it didn’t seem useful to cover preprocessors. Likewise, we’re not going to discuss documentation or guidelines, either, like code comments or formatting standards. Documentation is an entirely different topic that has more to do with maintenance than with optimization. Coding guidelines, as important as they are and as many of them we can set up, are often a matter of preference and don’t necessarily have a bearing on quality (for more on coding guidelines, see [_The Little Book of HTML/CSS Coding Guidelines_](https://www.oreilly.com/library/view/the-little-book/9781492048459/)). We’re already applying one of the mantras: keeping it simple.
66

0 commit comments

Comments
 (0)