From a6154697ba5a5ecb4256e318842aa331cfce17e4 Mon Sep 17 00:00:00 2001 From: rramthun Date: Sat, 9 Apr 2005 10:49:03 +0000 Subject: [PATCH] Fixed some grammar/spelling mistakes git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@8 6c8d7289-2bf4-0310-a012-ef5d649a1542 --- htroot/IndexMonitor.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/htroot/IndexMonitor.html b/htroot/IndexMonitor.html index 05f0804fb..bf3aeab98 100644 --- a/htroot/IndexMonitor.html +++ b/htroot/IndexMonitor.html @@ -30,14 +30,14 @@ #(process)#

Indexing Queues Monitor Overview

These are monitoring pages for the different indexing queues.

-

YaCy knows 5 different ways to aquire web indexes. The details of these processes (1-5) are described within the submenu's listed +

YaCy knows 5 different ways to acquire web indexes. The details of these processes (1-5) are described within the submenu's listed above which also will show you a table with indexing results so far. The information in these tables is considered as private, so you need to log-in with your administration password.

-

Case (6) is a monitor of the local receipt-generator, the opposed case of (1). It contains also a indexing result monitor but is not considered private +

Case (6) is a monitor of the local receipt-generator, the opposed case of (1). It contains also an indexing result monitor but is not considered private since it shows crawl requests from other peers.

-

The image above illustrates the data flow initiated by web index aquisition. +

The image above illustrates the data flow initiated by web index acquisition. Some processes occur double to document the complex index migration structure.

:: @@ -57,7 +57,7 @@ The index was crawled and contributed by other peers.

::

(3) Index Monitor for Index Transfer.

The url fetch was initiated and executed by other peers. -These links here have been transmitted to you because your peer ist most appropriate for storage according to +These links here have been transmitted to you because your peer is the most appropriate for storage according to the logic of the Global Distributed Hash Table.

Use Case: This list may fill if you check the 'Index Receive'-flag on the 'Index Control' page

:: @@ -67,7 +67,7 @@ the logic of the Global Distributed Hash Table.

such pages are detected by Cookie-Use or POST-Parameters (either in URL or as HTTP protocol) and automatically excluded from indexing.

Use Case: You must use YaCy as proxy to fill up this table. -Set your browser's proxy setting to the same port as given +Set the proxy settings of your browser to the same port as given on the 'Settings'-page in the 'Proxy and Administration Port' field.

::

(5) Index Monitor for Local Crawling.