You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ha...@apache.org on 2020/04/10 04:44:10 UTC

svn commit: r1876344 - /subversion/site/publish/docs/community-guide/releasing.part.html

Author: hartmannathan
Date: Fri Apr 10 04:44:10 2020
New Revision: 1876344

URL: http://svn.apache.org/viewvc?rev=1876344&view=rev
Log:
HACKING: Fix a couple of typos

* docs/community-guide/releasing.part.html
  (#before-release-pristine-tools): Fix "considereration" -> "consideration"
  (#releasing-signing-how): Fix "are encourages to" -> "are encouraged to"

Modified:
    subversion/site/publish/docs/community-guide/releasing.part.html

Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1876344&r1=1876343&r2=1876344&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Apr 10 04:44:10 2020
@@ -840,7 +840,7 @@ of this software as they are often patch
 portable.  The version numbers given above should normally be
 reconsidered and increased to the latest stable upstream release in
 the time leading up to an A.B.0 release.  Changing the version within
-an A.B.x series should only be done with careful considereration.</p>
+an A.B.x series should only be done with careful consideration.</p>
 
 <p><b>Autoconf, Libtool and SWIG</b>: Pick a directory to contain your
 special build tools for Subversion RM duties - for example
@@ -1122,7 +1122,7 @@ upload the signatures to the preliminary
 in the same directory as the tarballs.</p>
 
 <p>
-Members of the PMC, as well as enthusiastic community members are encourages to
+Members of the PMC, as well as enthusiastic community members are encouraged to
 download the tarballs from the preliminary distribution location, run the
 tests, and then provide their signatures.  The public keys for these signatures
 should be included in the ASF LDAP instance through