svn commit: r1141987 - in /subversion/site/publish/docs/community-guide: releasing.part.html roles.part.html

[danielsh]

Author: danielsh
Date: Fri Jul  1 16:41:47 2011
New Revision: 1141987

URL: http://svn.apache.org/viewvc?rev=1141987&view=rev
Log:
* docs/community-guide/releasing.part.html,
  docs/community-guide/roles.part.html:
    Fix broken links to #lightweight-branches.

Modified:
    subversion/site/publish/docs/community-guide/releasing.part.html
    subversion/site/publish/docs/community-guide/roles.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=1141987&r1=1141986&r2=1141987&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Jul  1 
16:41:47 2011
@@ -321,7 +321,7 @@ confusion caused by your custom release.
 <p>Second, consider creating a branch in the public Subversion
 repository to track your changes and to potentially allow your custom
 changes to be merged into mainline Subversion.  (If you do not have it
-already, <a href="<!--#echo var="GUIDE_ROLES_PAGE" -->#lightweight-branches"
+already, <a href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#lightweight-branches"
 >ask for commit access</a>.)</p>
 
 <p>Third, if your custom release is likely to generate bug reports

Modified: subversion/site/publish/docs/community-guide/roles.part.html
URL: 
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/roles.part.html?rev=1141987&r1=1141986&r2=1141987&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/roles.part.html (original)
+++ subversion/site/publish/docs/community-guide/roles.part.html Fri Jul  1 
16:41:47 2011
@@ -107,8 +107,8 @@ committers, actually&nbsp;&mdash; view s
 grounds for new developers, by giving feedback on the commits.  The
 goal of these branches is both to get new code into Subversion and to
 get new developers into the project.  See also the <a
-href="<!--#echo var="GUIDE_ROLES_PAGE" -->#lightweight-branches" >section on 
lightweight branches</a>, and
-this mail:</p>
+href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#lightweight-branches"
+>section on lightweight branches</a>, and this mail:</p>
 
 <pre>
    <a 
href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&amp;msgNo=132746";