From: eldy <> Date: Sun, 24 Mar 2002 13:38:48 +0000 (+0000) Subject: Spells corections in docs X-Git-Tag: AWSTATS_4_0_BETA~29 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fc2775fa7bfae87fb86c363da0e93fac5f3ce220;p=thirdparty%2FAWStats.git Spells corections in docs --- diff --git a/docs/awstats_faq.html b/docs/awstats_faq.html index ac384131..ba44a462 100644 --- a/docs/awstats_faq.html +++ b/docs/awstats_faq.html @@ -342,7 +342,7 @@ but I have no image shown.
SOLUTION: With Apache web server, you might have troubles (no picture shown on stats page) if you use a directory called "icons" (because of Apache pre-defined "icons" alias directory), so use instead, for example, a directory called "icon" with -no s at the end (Rename your directory phisically and change the DirIcons parameter in config file +no s at the end (Rename your directory physically and change the DirIcons parameter in config file to reflect this change).

@@ -421,7 +421,7 @@ All benchmarks information and advice on frequency for update process are relate
FAQ-COM200 : HOW REVERSE DNS LOOKUP WORKS, UNRESOLVED IP ADDRESSES
PROBLEM: The reported page AWStats shows me -has no hostnames, only IP addresses, countries reported are all "unkown".
+has no hostnames, only IP addresses, countries reported are all "unknown".
SOLUTION: When AWStats find an IP address in your log file, it tries a reverse DNS lookup to find the hostname and domain if the DNSLookup parameter, in your AWStats config file, is DNSLookup=1 diff --git a/docs/awstats_security.html b/docs/awstats_security.html index 048f067d..5b14f5e3 100644 --- a/docs/awstats_security.html +++ b/docs/awstats_security.html @@ -46,7 +46,7 @@ of them. You don't need that your customer have "real-time" statistics.
This is a very good choice for web hosting providers with few but very large web sites of important customers.
Advantage:
Very highly secured.
-Disavdantage:
+Disadvantage:
Statistics are static, no dynamic update/view.
How:
All statistics pages for a config/domain file are built in static html files using -output -staticlinks option.
@@ -72,9 +72,9 @@ be made (if allowed) on-line.
No way to have 2 configurations files for 1 particular domain.
How:
First, AWStats must be placed in its own cgi-bin-awstats directory with no way for users to -put in it a hacked verion of AWStats (a not writeable directory).
+put in it a hacked version of AWStats (a not writable directory).
Then, you must add an environment variable called AWSTATS_CONFIG in the web server environment -for each domain to say wich config file to use for a particular domain.
+for each domain to say which config file to use for a particular domain.
With Apache web server, you must use the 'SetEnv' directive. This is an example:
<VirtualHost www.xxx.yyy.zzz>
  ServerAdmin webmaster@mydomain.com
@@ -90,10 +90,10 @@ even if a visitor try to force the config file with the URL 'http://mydomain.
3) MEDIUM SECURED
-!!! This policy is not possible yet as the use of file awstatsusers is not yet developped. !!!
+!!! This policy is not possible yet as the use of file awstatsusers is not yet developed. !!!
Policy:
-You have several config/domain and several users. You want to specify (using a awstatsusers file) wich user can see -or update dinamically statistics for each config/domain.
+You have several config/domain and several users. You want to specify (using a awstatsusers file) which user can see +or update dynamically statistics for each config/domain.
Advantage:
Statistics are dynamic. High level of manageability.
Disadvantage:
diff --git a/docs/awstats_setup.html b/docs/awstats_setup.html index 74088f48..596a62ac 100644 --- a/docs/awstats_setup.html +++ b/docs/awstats_setup.html @@ -55,7 +55,7 @@ logresolvemerge.pl and the lang and db sub-directories).
to reflect the path were your perl interpreter is installed.
Default value works for most of Unix OS, but it also might be
#!/usr/local/bin/perl
-With Apache for Windows and Activeperl interpreter, it might be
+With Apache for Windows and ActivePerl interpreter, it might be
#!c:/program files/activeperl/bin/perl

* Move all awstats icon sub-directories into a directory readable by your @@ -105,7 +105,7 @@ Or, you can view dynamically your statistics from a browser. For this, if you named your config file awstats.conf, just use URL:
http://www.myserver.mydomain/cgi-bin/awstats.pl If you named your config file awstats.virtualhostname.conf, use URL:
-http://www.myserver.mydomain/cgi-bin/awstats.pl?config=virtualhost +http://www.myserver.mydomain/cgi-bin/awstats.pl?config=virtualhostname where virtualhostname is used to know which config file to use (AWStats will use awstats.virtualhostname.conf file).

diff --git a/docs/awstats_what.html b/docs/awstats_what.html index 0cb85fb8..f506ee9c 100644 --- a/docs/awstats_what.html +++ b/docs/awstats_what.html @@ -38,14 +38,14 @@
A full log analysis enables AWStats to show you the following information:
* Number of VISITS, and UNIQUE VISITORS, list of last visits,
- * Days of week and Rush hours (pages, hits, kb for each hour and day of week),
- * Domains/countries of hosts visitors (pages, hits, kb, 259 domains/countries detected),
+ * Days of week and Rush hours (pages, hits, KB for each hour and day of week),
+ * Domains/countries of hosts visitors (pages, hits, KB, 259 domains/countries detected),
* Authenticated users,
* Most often pages viewed and entry pages,
* File types,
* Web compression statistics (for mod_gzip),
- * Browsers used (pages, hits, kb for each browser, each version, 72 browsers: Web, Wap, Media browsers...),
- * OS used (pages, hits, kb for each OS, 28 OS detected),
+ * Browsers used (pages, hits, KB for each browser, each version, 72 browsers: Web, Wap, Media browsers...),
+ * OS used (pages, hits, KB for each OS, 28 OS detected),
* VISITS OF ROBOTS (287 robots detected),
* SEARCH ENGINES, Keyphrases or Keywords used to find your site (The 57 most famous search engines are detected like yahoo, google, altavista, etc...),
* HTTP errors (Page Not Found, ...),
@@ -54,7 +54,7 @@ * Can analyze a lot of log formats: Apache NCSA combined log files (XLF/ELF) or common (CLF), IIS log files (W3C), WebStar native log files and other web, proxy or wap servers log files). See AWStats F.A.Q. for examples.
* Works from command line and from a browser as a CGI,
* Update of statistics can be made from a web browser and not only from your scheduler,
- * Unlimited log file size, support splited log files (load balancing system),
+ * Unlimited log file size, support split log files (load balancing system),
* Reverse DNS lookup during analysis,
* A lot of options/filters can be defined,
* Multi-named web sites supported (virtual servers, great for web-hosting providers),