You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@subversion.apache.org by cm...@apache.org on 2012/07/19 16:44:49 UTC

svn commit: r1363357 - /subversion/trunk/notes/authz_policy.txt

Author: cmpilato
Date: Thu Jul 19 14:44:49 2012
New Revision: 1363357

URL: http://svn.apache.org/viewvc?rev=1363357&view=rev
Log:
* notes/authz_policy.txt
  (REVISION PROPERTIES): Fix a typo.

Reported by: kameshj

Modified:
    subversion/trunk/notes/authz_policy.txt

Modified: subversion/trunk/notes/authz_policy.txt
URL: http://svn.apache.org/viewvc/subversion/trunk/notes/authz_policy.txt?rev=1363357&r1=1363356&r2=1363357&view=diff
==============================================================================
--- subversion/trunk/notes/authz_policy.txt (original)
+++ subversion/trunk/notes/authz_policy.txt Thu Jul 19 14:44:49 2012
@@ -120,7 +120,7 @@ WHAT USERS SHOULD EXPECT FROM PATH-BASED
    modified in that revision.  It is precisely because Subversion
    tries not to reveal unreadable paths to users that revprop access
    is limited as described above.  So as long as the user has the
-   requisite read access to the changed-paths, it's okay if he or see
+   requisite read access to the changed-paths, it's okay if he or she
    lacks write access to one or more of those paths when attempting to
    set or change revprops -- the information Subversion is trying to
    protect through its revprop access control is considered safe to