svn commit: r1910900 - /subversion/site/staging/faq.html

[ha...@apache.org]

Author: hartmannathan
Date: Sun Jul  9 14:41:44 2023
New Revision: 1910900

URL: http://svn.apache.org/viewvc?rev=1910900&view=rev
Log:
In site/staging, improve (hopefully) the new reverse proxy instructions in FAQ

* faq.html
  (#reverseproxy): Follow-up to r1910877, r1910878, r1910881, and r1910882.
   Remove out-of-place "A custom" which seems to be left over from earlier
   editing. Fix a few minor nits with punctuation and one spelling typo.

Modified:
    subversion/site/staging/faq.html

Modified: subversion/site/staging/faq.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/faq.html?rev=1910900&r1=1910899&r2=1910900&view=diff
==============================================================================
--- subversion/site/staging/faq.html (original)
+++ subversion/site/staging/faq.html Sun Jul  9 14:41:44 2023
@@ -949,15 +949,15 @@ running <tt>svn --version</tt>.</p>
 connected to the internet. It will forward HTTP/HTTPS traffic from a public
 facing server to the Subversion server, potentially removing HTTPS
 encryption. It can also be useful if several different HTTP servers must
-to be served on the same port.</p>
+be served on the same port.</p>
 
-<p>Subversion use a subset of the WebDAV/DeltaV protocol, see <a 
-href="#http-methods">this FAQ item</a> for the details. A custom
-As far as the proxy server is concerned, Subversion use plain WebDAV
+<p>Subversion uses a subset of the WebDAV/DeltaV protocol; see <a 
+href="#http-methods">this FAQ item</a> for the details.
+As far as the proxy server is concerned, Subversion uses plain WebDAV
 protocol. For the <tt>svn copy</tt> and <tt>svn move</tt> commands, an extra 
-HTTP_DESTINATION header is used, this must be rewritten separately.</p>
+HTTP_DESTINATION header is used; this must be rewritten separately.</p>
 
-<p>Detailed instructions are provided for a few different proxy servers, it
+<p>Detailed instructions are provided for a few different proxy servers. It
 should be fairly easy to copy the ideas from these examples.</p>
 
 <h4>Detailed instructions for Apache HTTPD</h4>
@@ -1006,13 +1006,13 @@ ProxyPass /svn/ http://realsvnserver/svn
 <p>The ProxyPass directive tells Apache to redirect requests below /svn to
 the subversion-Apache (http://realsvnserver/svn). The ProxyPassReverse
 directive tells it to alter the request headers (Location, Content-Location,
-and URI) to match the target server - depending on your version of Apache and
+and URI) to match the target server &mdash; depending on your version of Apache and
 its configuration you may need to leave out either /svn/ or
 http://realsvnserver/svn/. If possible the same path should be used on both
 servers (otherwise DAV might make trouble). The Limit directive tells Apache
 to let all DAV requests from all clients (Allow) through and let the real
 subversion server handle authentication (Satisfy). The Rewrite rules
-update the HTTP_DESTINATION header to the corrent server/protocol.</p>
+update the HTTP_DESTINATION header to the correct server/protocol.</p>
 
 <h4>Detailed instructions for Microsoft IIS</h4>
 
@@ -1025,7 +1025,7 @@ Variables and add HTTP_DESTINATION.<br/>
 Finally create a few rewrite rules:
 <ul>
 <li>"ToHttps", if you would like to ensure all Subversion traffic is
-encrypted, this send an HTTP redirect to the client if the request is sent
+encrypted, this sends an HTTP redirect to the client if the request is sent
 unencrypted.</li>
 <li>"ProxyWithDestination", capturing all requests with the HTTP_DESTINATION
 server variable (ie. all <tt>svn copy</tt> and <tt>svn move</tt> requests).