On Monday, I received comments from the proofreader of the blogdown manuscript. There were 376 comments in the PDF, and that was much more than I expected! I have worked with Chapman & Hall a few times before, and I knew the proofreader would let me make changes like:
-
Change “I recommend you to do something” to “I recommend that you do something”.
-
Add “that” after “Note”, e.g., “Note that you should …” instead of “Note you should …”.
-
Always move punctuations before double quotes (note that the positions of periods in the above two bullets are wrong!), and move footnote numbers after punctuations.
For some reason, I still forgot these things when I wrote the book. Anyway, I spent four hours on correcting these problems and returned the revised manuscript in the late night on Monday. I guess this book should be available for sale in January next year, thanks to my amazing proofreader Rebecca (Becky) Condit and production manager Suzanne Lassandro at Chapman & Hall. My editor John Kimmel told me “[…] no other books are getting published this fast.”
Becky is a truly professional proofreader. Occasionally I laughed at myself while working through her comments. Below are two examples that show how awkward my English writing can be sometimes.
She changed
“For a theme author aware of the fact that users may customize her theme, she will typically provide two ways: […]”
to
“A theme author who is aware of the fact that users may customize her theme will typically provide two ways: […]”
My original sentence feels so fragmented, and she made it much smoother. She also changed
“There is an internal helper function
blogdown:::modify_yaml(), which may help you clean up the metadata.”
to
“The internal helper function
blogdown:::modify_yaml()may help you clean up the metadata.”
Straight to the point! Why did I use such an awkward clause?

It is a blessing to have a proofreader like Becky to help me. There are so many unsung heroes and heroines in this world. I’m hoping to write more about them in the future.
Donate
As a freelancer (currently working as a contractor) and a dad of three kids, I truly appreciate your donation to support my writing and open-source software development! Your contribution helps me cope with financial uncertainty better, so I can spend more time on producing high-quality content and software. You can make a donation through methods below.
-
Venmo:
@yihui_xie, or Zelle:xie@yihui.name -
Paypal
-
If you have a Paypal account, you can follow the link https://paypal.me/YihuiXie or find me on Paypal via my email
xie@yihui.name. Please choose the payment type as “Family and Friends” (instead of “Goods and Services”) to avoid extra fees. -
If you don’t have Paypal, you may donate through this link via your debit or credit card. Paypal will charge a fee on my side.
-
-
Other ways:
WeChat Pay (微信支付:谢益辉) Alipay (支付宝:谢益辉) 

When sending money, please be sure to add a note “gift” or “donation” if possible, so it won’t be treated as my taxable income but a genuine gift. Needless to say, donation is completely voluntary and I appreciate any amount you can give.
Please feel free to email me if you prefer a different way to give. Thank you very much!
I’ll give back a significant portion of the donations to the open-source community and charities. For the record, I received about $30,000 in total (before tax) in 2024-25, and gave back about $15,000 (after tax).