I’m so excited to announce the next book in the Adventures in Writing series: 10 Core Practices for Better Writing.
About the Book:
Writing is an adventure that lasts a lifetime.
Start your adventure with 10 Core Practices for Better Writing, a book that helps you strengthen your writing skills so you can excel in the craft of writing.
You’ll develop simple but effective habits that will consistently improve your writing — core practices that will stay with you forever.
It doesn’t matter whether you write fiction, poetry, or nonfiction. The practices outlined in this book give you the tools and techniques you need to consistently produce better writing over time. Every project you write will be better than the last.
Ideal for new and experienced writers alike, this book will enlighten and inform your work. It’s perfect for writing groups, classes, and workshops as well as individual writers who want to bring their writing to the professional level.
You’ll find inspirational quotes, questions for thought and discussion, and activities peppered throughout.
10 Core Practices for Better Writing
Start your journey toward better writing today.
10 Core Practices for Better Writing is now available in paperback and for the Kindle at Amazon, and it will be coming soon to other online bookstores, including Smashwords, Sony, Barnes & Noble, Kobo, and Apple’s iBookstore. I’ll make an announcement here on the blog as soon as the book is available everywhere.
Amazon Paperback |
Amazon Kindle |
This post contains affiliate links.
Sign up here to receive notifications when new books are available.
Congratulations on having a new book out!
Thanks, Kelvin!
Thanks for the post. Always interested in various perspectives on writing, so am picking this up. As you put it well, different things work for different people. Congrats on the release. Also, the “paperback” link above goes to your other book, not the new one. Cheers!
Thanks, Ryan. I hope you enjoy the book and find it useful. Also, thanks for alerting me to the incorrect link. It’s fixed now 🙂