<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I agree wholeheartedly with Doug’s request. Acronyms and abbreviations should be like pronouns and always have an antecedent. The <a href="https://blog.apastyle.org/apastyle/abbreviations/" class="">American Psychological Association Style Guide</a> has useful guidelines.<div class=""><br class=""></div><div class="">Tom Benedict</div><div class="">Seahurst, WA<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 28, 2022, at 19:05, Doug Santoni <<a href="mailto:dougsantoni@gmail.com" class="">dougsantoni@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I love getting news of Washingtonn bird sightings on both Tweeters and E-Bird, and I’m grateful for all of this great information…but wondering if posters could please try to help some of us out by avoiding cryptic acronyms and abbreviations. A recent Union Bay sighting referred to a “ho” near “UHC” (this sounds a bit unsavory), and I just saw comments, again relating to Union Bay, on K2 (isn’t that a mountain in the Himalayas?), which left me completely befuddled. Could I kindly ask that posters be sympathetic to those of us who may not be in on this insiders’ language?<br class=""><br class="">Doug Santoni<br class="">Seattle, WA<br class="">Dougsantoni at gmail dot com<br class=""></div></div></blockquote></div><br class=""></div></body></html>