X-Git-Url: http://git.indexdata.com/?p=idzebra-moved-to-github.git;a=blobdiff_plain;f=doc%2Farchitecture.xml;h=5b3a27ebd2b5cc89cc08f7225dca9864c90487be;hp=3f8ad6db9eb570a27384e3face0bbc609da66eb4;hb=31b0ba1ecb737f9db4cf3340e93964c6679897fd;hpb=1d2919b93a4835aa36ad39f32c1bdeb34fdcb142

diff --git a/doc/architecture.xml b/doc/architecture.xml
index 3f8ad6d..5b3a27e 100644
--- a/doc/architecture.xml
+++ b/doc/architecture.xml
@@ -1,5 +1,4 @@
  <chapter id="architecture">
-  <!-- $Id: architecture.xml,v 1.26 2007-12-19 13:35:39 adam Exp $ -->
   <title>Overview of &zebra; Architecture</title>
 
   <section id="architecture-representation">
@@ -221,7 +220,7 @@
     </para>
     <para>
       The internal &acro.dom; &acro.xml; representation can be fed into four
-      different pipelines, consisting of arbitraily many sucessive
+      different pipelines, consisting of arbitrarily many successive
       &acro.xslt; transformations; these are for  
      <itemizedlist>
        <listitem><para>input parsing and initial
@@ -292,8 +291,8 @@
       static ranks. This imposes no overhead at all, both
       search and indexing perform still 
       <emphasis>O(1)</emphasis> irrespectively of document
-      collection size. This feature resembles Googles pre-ranking using
-      their Pagerank algorithm.
+      collection size. This feature resembles Google's pre-ranking using
+      their PageRank algorithm.
     </para>
     <para>
       Details on the experimental Alvis &acro.xslt; filter are found in 
@@ -443,7 +442,7 @@
     &zebra;'s internal index structure/data for a record.
     In particular, the regular record filters are not invoked when
     these are in use.
-    This can in some cases make the retrival faster than regular
+    This can in some cases make the retrieval faster than regular
     retrieval operations (for &acro.marc;, &acro.xml; etc).
    </para>
    <table id="special-retrieval-types">
@@ -565,7 +564,7 @@
       Z> elements zebra::meta
       Z> s 1+1
     </screen> 
-    displays all available metadata on the record. These include sytem
+    displays all available metadata on the record. These include system
     number, database name,  indexed filename,  filter used for indexing,
     score and static ranking information and finally bytesize of record.
    </para>