svn commit: r1027347 - in /websites/staging/httpd/trunk/content: ./ docs-project/index.html

[bu...@apache.org]

Author: buildbot
Date: Sun Mar 25 15:38:58 2018
New Revision: 1027347

Log:
Staging update by buildbot for httpd

Modified:
    websites/staging/httpd/trunk/content/   (props changed)
    websites/staging/httpd/trunk/content/docs-project/index.html

Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Mar 25 15:38:58 2018
@@ -1 +1 @@
-1827722
+1827723

Modified: websites/staging/httpd/trunk/content/docs-project/index.html
==============================================================================
--- websites/staging/httpd/trunk/content/docs-project/index.html (original)
+++ websites/staging/httpd/trunk/content/docs-project/index.html Sun Mar 25 15:38:58 2018
@@ -134,7 +134,7 @@ love to have your help too.</p>
 </ul>
 <h1 id="report">Reporting a problem<a class="headerlink" href="#report" title="Permanent link">&para;</a></h1>
 <p>The best way to report a problem with the documentation is to make a comment
-on the docs page in question, or to <a href="https://issues.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2">open a
+on the docs page in question, or to <a href="https://bz.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2&amp;component=Documentation">open a
 ticket</a>.
 Select 'Documentation' as the component. Have a look at the <a href="http://s.apache.org/httpd-doc-bugs">list of open
 documentation bugs</a> to see if it's
@@ -145,7 +145,7 @@ to write a new or replacement document,
 about it.</p>
 <p>The best way is probably to <a href="#ml">join the mailing list</a> and strike up a
 conversation. We always love to have new people on the project.</p>
-<p>Or, you can <a href="#problem">open a ticket</a> , as discussed above. We are very
+<p>Or, you can <a href="#report">open a ticket</a> , as discussed above. We are very
 interested in your suggestions, and any way that you think we can improve
 the documentation. We look forward to hearing from you.</p>
 <p>The 2.2, 2.4 and trunk documentation also have a comment feature, where