You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ja...@apache.org on 2015/07/11 06:39:42 UTC
svn commit: r1690343 - /httpd/httpd/trunk/docs/manual/getting-started.xml
Author: jailletc36
Date: Sat Jul 11 04:39:42 2015
New Revision: 1690343
URL: http://svn.apache.org/r1690343
Log:
Fix doc as spotted by Matthew in online doc
Modified:
httpd/httpd/trunk/docs/manual/getting-started.xml
Modified: httpd/httpd/trunk/docs/manual/getting-started.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/getting-started.xml?rev=1690343&r1=1690342&r2=1690343&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/getting-started.xml (original)
+++ httpd/httpd/trunk/docs/manual/getting-started.xml Sat Jul 11 04:39:42 2015
@@ -197,7 +197,7 @@ problem without the error log is like dr
module="core">ErrorLog</directive> directive, which may be set globally,
or per virtual host. Entries in the error log tell you what went wrong,
and when. They often also tell you how to fix it. Each error log message
-contains a error code, which you can search for online for even more
+contains an error code, which you can search for online for even more
detailed descriptions of how to address the problem. You can also
configure your error log to contain a log ID which you can then
correlate to an access log entry, so that you can determine what request