Clarification touchup

docs/content/contribute/styleguide.md

@@ -215,7 +215,7 @@ Obviously an exception to this rule is when a document uses (possibly defines) c
 
 NIST has requirements regarding license statements and disclaimers, which might apply if you are publishing software (considered broadly as anything executable in some fashion). You should see to it that all copyright and licensing-related guidelines are adhered to: see https://www.nist.gov/open/copyright-fair-use-and-licensing-statements-srd-data-software-and-technical-series-publications.
 
-Keep in mind these requirements apply for both providing licenses, and for acquiring permissions if and where necessary to abide by implicit or explicit licensing terms including copyright terms. Since our works go into the public domain, to publish on our sites is to put something into the public domain; so be sure you have a right to do that or you have explicitly carved out the exception with the rights holder.
+Keep in mind these requirements apply for both providing licenses, and for acquiring permissions if and where necessary to abide by implicit or explicit licensing terms including copyright terms. Since our works go into the public domain, to publish on our sites is to put something into the public domain; so be sure you have a right to do this (fair use with citation counts as a right) or you have explicitly secured rights from the owner.
 
 A word about citations is also given in its [own section](#citations-and-links).