Changeset 30302

Show
Ignore:
Timestamp:
02/19/08 18:34:29 (9 months ago)
Author:
sfermigier
Message:

Fix typos.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • doc/nuxeo-book/trunk/src/docbook/actions-views/index.xml

    r26476 r30302  
    383383    <title>Nuxeo JSF tags</title> 
    384384 
    385     <para>Please refer to the tag livbrary documentation available at <link 
     385    <para>Please refer to the tag library documentation available at <link 
    386386    xlink:href="http://maven.nuxeo.org/nuxeo-platform-parent/nuxeo-platform-ui-web/tlddoc/index.html">http://maven.nuxeo.org/nuxeo-platform-parent/nuxeo-platform-ui-web/tlddoc/index.html</link>.</para> 
    387387  </section> 

  • doc/nuxeo-book/trunk/src/docbook/admin/virtualhosting.xml

    r27437 r30302  
    4040 
    4141          <para>Nuxeo 5 generate standard http cache headers for all static 
    42           resources (images, javascripts ...).</para> 
     42          resources (images, JavaScript...).</para> 
    4343 
    4444          <para>These resources are by default cached on the client side (in 
    45           the browser cache), for performances reason, it can be usefull to 
     45          the browser cache), for performances reason, it can be useful to 
    4646          host these resources in the reverse proxy cache.</para> 
    4747        </listitem> 
    …… 
    4949  </section> 
    5050  <section> 
    51     <title id="" xreflabel="Apache2 configuration">Configuration Virtual hosting with Apache2</title> 
     51    <title id="" xreflabel="Apache2 configuration">Configuration Virtual hosting with Apache 2</title> 
    5252 
    5353  <section> 
    …… 
    6565    </para> 
    6666    <para> 
    67     Unfortutly this header does not include the protocol, so if your apache is https, you will need to send, Nuxeo5 a dedicated header to indicate the base URL that the webapp ust use when generating links. 
     67    Unfortunately this header does not include the protocol, so if your apache is https, you will need to send, Nuxeo 5 a dedicated header to indicate the base URL that the webapp must use when generating links. 
    6868    </para> 
    6969    <programlisting> 
    …… 
    110110  <section> 
    111111    <title>Configuring http cache </title> 
    112  <para></para> 
     112    <para></para> 
    113113    <programListing> 
    114114    </programListing> 
    …… 
    117117  </section> 
    118118 
    119  
    120119   </section> 
    121120</chapter> 

  • doc/nuxeo-book/trunk/src/docbook/administration/admin-database-configuration.xml

    r25585 r30302  
    1717  <itemizedlist> 
    1818      <listitem> 
    19         <para>install the JDBC driver,</para> 
     19        <para>install the JDBC driver for your DBMS,</para> 
    2020      </listitem> 
    2121 
    2222      <listitem> 
    23         <para>configure Nuxeo Core storage, modifying the default repository 
     23        <para>configure the Nuxeo Core storage, modifying the default repository 
    2424        configuration,</para> 
    2525      </listitem> 

  • doc/nuxeo-book/trunk/src/docbook/administration/admin-specific_IP_binding-configuration.xml

    r27919 r30302  
    1919      <filename>$JBOSS_HOME/server/default/deploy/nuxeo.ear/config/nuxeo.properties</filename> 
    2020      change the value of <varname>org.nuxeo.ecm.instance.host</varname>, 
    21       remplace "localhost" by the IP adress of the Jboss server</para> 
     21      remplace "localhost" by the IP adress of the JBoss server</para> 
    2222    </listitem> 
    2323 

  • doc/nuxeo-book/trunk/src/docbook/administration/index.xml

    r29590 r30302  
    139139 
    140140    <para>Note that the platform used for both the JVM and OOo have to be 
    141     consistent to allow UNO protocol to work : with a 32 bits JVM, you'll have 
    142     to use the 32 bits OOo verson while the 64 bits one will be mandatory for 
     141    consistent to allow UNO protocol to work: with a 32 bits JVM, you'll have 
     142    to use the 32 bits OOo version while the 64 bits one will be mandatory for 
    143143    a 64 bits JVM.</para> 
    144144  </section> 

  • doc/nuxeo-book/trunk/src/docbook/architecture-overview/index.xml

    r27437 r30302  
    4747              <listitem> 
    4848                <para>In order to be easily hostable, the platform need to be 
    49                 compatbible with several application servers</para> 
     49                compatible with several application servers</para> 
    5050              </listitem> 
    5151            </itemizedlist> 
    …… 
    358358            <para>This mainly means synchronous or asynchronous events 
    359359            listener that are a great place to handle communication and 
    360             synchronisation between applications.</para> 
     360            synchronization between applications.</para> 
    361361          </listitem> 
    362362        </itemizedlist> 
    …… 
    477477        some platform that don't handle this (like Java EE).</para> 
    478478 
    479         <para>This is one of the motivation for the NXRuntime that will be 
     479        <para>This is one of the motivation for the Nuxeo Runtime that will be 
    480480        quickly introduce later in this document.</para> 
    481481      </section> 
    …… 
    637637 
    638638  <section> 
    639     <title>NXRuntime: Nuxeo EP component model</title> 
     639    <title>Nuxeo Runtime: the Nuxeo EP component model</title> 
    640640 
    641641    <section> 
    …… 
    730730 
    731731                <para>Because Nuxeo EP is extensible and has a plugin model, 
    732                 we need that feature. A contribution is dependant on the 
     732                we need that feature. A contribution is dependent on the 
    733733                component it contribute to:</para> 
    734734 
    …… 
    13511351      role="bold">deployment strategy</emphasis></para> 
    13521352 
    1353       <para>Thanks to the NXRuntime remoting features it is very easy to split 
     1353      <para>Thanks to the Nuxeo Runtime remoting features it is very easy to split 
    13541354      the components on several JVM. But splitting some services can have a 
    13551355      very bad effect on the global system performance.</para> 
    …… 
    14761476        several Maven 2 artifact.</para> 
    14771477 
    1478         <para>Nuxeo packaging and deployment system (NXRuntime, Plateform API, 
     1478        <para>Nuxeo packaging and deployment system (Nuxeo Runtime, Platform API, 
    14791479        Maven ...) leverage this separation to help you distributing the 
    14801480        needed deployment unit according to your target physical 
    …… 
    15401540              <title>Nuxeo Repository Service</title> 
    15411541              <para> The repository service let you define new document repositories. Defining separated repositories for your documents is pretty much like defining separated Databases for your records.</para> 
    1542               <para> Because Nuxeo Core defines a SPI on repository, you can configure how you want the repository to be implemented. For now, default implementation uses JSR-170 (Java Content Repository) reference implementation : Apache Jack Rabbit. In the future, we may provide other implementation of the Repostory SPI (like native SQL DB or Object Oriented DB).</para> 
    1543               <para> Even if for now there is only one Repository implementation available, using JCR implementation, you can configure how your data will be persisted : filesystem, xml or SQL Database. Please see "How too"s about repository configuration.</para> 
    1544               <para> When definining a new repository, you can configure :   
     1542              <para> Because Nuxeo Core defines a SPI on repository, you can configure how you want the repository to be implemented. For now, default implementation uses JSR-170 (Java Content Repository) reference implementation : Apache Jack Rabbit. In the future, we may provide other implementation of the Repository SPI (like native SQL DB or Object Oriented DB).</para> 
     1543              <para> Even if for now there is only one Repository implementation available, using JCR implementation, you can configure how your data will be persisted : filesystem, xml or SQL Database. Please see "How to"s about repository configuration.</para> 
     1544              <para> When defining a new repository, you can configure :   
    15451545                  <itemizedlist> 
    15461546                    <listitem> 
    …… 
    15801580 
    15811581                    <listitem> 
    1582                       <para>An optionnal super document type (inheritence)</para> 
     1582                      <para>An optional super document type (inheritance)</para> 
    15831583                    </listitem> 
    15841584 
    …… 
    15901590                    <listitem> 
    15911591                      <para>A list of facets</para> 
    1592                       <para>Simple markers used to define document behaviour.</para> 
     1592                      <para>Simple markers used to define document behavior.</para> 
    15931593                    </listitem> 
    15941594                  </itemizedlist> 
    …… 
    16091609    </programlisting> 
    16101610 
    1611      For further explaination on Schemas and Document types, please see the dedicated section in this document. 
     1611     For further explanation on Schemas and Document types, please see the dedicated section in this document. 
    16121612    </para> 
    16131613    </section> 

  • doc/nuxeo-book/trunk/src/docbook/core-io/index.xml

    r25371 r30302  
    8383      the XML file in their own file.</para>  
    8484       
    85       <para>So instead of enconding the blob in the XML file a reference to an 
     85      <para>So instead of encoding the blob in the XML file a reference to an 
    8686      external file is preserved: cd1f161f.blob</para> 
    8787 
    …… 
    129129 
    130130      <listitem> 
    131         <para>transforming the data if necesarly</para> 
     131        <para>transforming the data if necessary</para> 
    132132      </listitem> 
    133133 
    …… 
    146146 
    147147      <listitem> 
    148         <para>transforming the data if necesarly</para> 
     148        <para>transforming the data if necessary</para> 
    149149      </listitem> 
    150150 
    …… 
    234234          <listitem> 
    235235            <para>DocumentListReader - this one is taking as input a list of 
    236             document models and export them as domj Documents. This is usefull 
     236            document models and export them as domj Documents. This is useful 
    237237            when wanting to export a search result for example.</para> 
    238238          </listitem> 
    …… 
    249249            <para>XMLDirectoryReader - read a directory tree in the format 
    250250            supported by Nuxeo (as described in <xref 
    251             linkend="exportFormat" /> section). YThis can be used to import 
    252             defalted nuxeo archives or hand created document 
     251            linkend="exportFormat" /> section). This can be used to import 
     252            deflated nuxeo archives or hand created document 
    253253            directories.</para> 
    254254          </listitem> 
    …… 
    261261 
    262262          <listitem> 
    263             <para>ZipReader - read a zip archive and output DOM objects.This 
     263            <para>ZipReader - read a zip archive and output DOM objects. This 
    264264            reader can read both Nuxeo zip archives and regular zip archives 
    265265            (hand made). Reading a Nuxeo archive is more optimized - because 
    …… 
    267267            predefined order that makes possible reading the entire archive 
    268268            tree on the fly without unziping the content of the archive on the 
    269             file systemn first. If the zip archive is not recognized as a 
    270             Nuxeo archive the zip will be defalted in a temporary folder on 
     269            filesystem first. If the zip archive is not recognized as a 
     270            Nuxeo archive the zip will be deflated in a temporary folder on 
    271271            the file system and the XMLDirectoryReader will be used to read 
    272272            the content.</para> 
    …… 
    283283    <title>Document Writer</title> 
    284284 
    285     <para>A document writer is repsonsible to write the documents that exit 
     285    <para>A document writer is responsible to write the documents that exit 
    286286    the pipe in a document store. This storage can be a File System, A Nuxeo 
    287287    Repository or any database or data storage as long as you have a writer 
    …… 
    354354    <title>Document Transformer</title> 
    355355 
    356     <para>Document transformers are useful to transform documents thaty enter 
     356    <para>Document transformers are useful to transform documents that enter 
    357357    the pipe and before being sent to the writer. This way you can remove, add 
    358358    or modify some properties from the documents, or other information 

  • doc/nuxeo-book/trunk/src/docbook/coredevguide-book.xml

    r24889 r30302  
    4848        <para>The first time, you need to add some Nuxeo libraries into the 
    4949        JBoss directory, so you first run, from the top of your nuxeo-ep 
    50         checkout: <programlisting>$ cd nuxeo-ep 
     50        checkout: 
     51        <programlisting>$ cd nuxeo-ep 
    5152$ ant patch</programlisting> 
    5253        then: 
    …… 
    6869        <para>From the top of your <filename>nuxeo-ep</filename> checkout, 
    6970        after having done a <command>svn up</command>, to build the updated 
    70         platform you need to execute only: <programlisting>$ cd nuxeo-ep 
    71 $ ant </programlisting></para> 
     71        platform you need to execute only: 
     72        <programlisting>$ cd nuxeo-ep 
     73$ ant </programlisting> 
     74        </para> 
    7275      </section> 
    7376 

  • doc/nuxeo-book/trunk/src/docbook/workflow-service/deploy-process-definitions.xml

    r29472 r30302  
    1414  specify a new process definition language. Thus it has no Nuxeo 
    1515  specificities speaking of format or process definition language. For 
    16   instance, if you use jBPM as a backend with Nuxeo5 then the workflow 
     16  instance, if you use jBPM as a backend with Nuxeo 5 then the workflow 
    1717  definition should be a standard jpdl file that you may have designed using 
    1818  your favorite editor or still if you are using Shark as a backend then the 
    …… 
    2828 
    2929    <para>The Nuxeo workflow service provides a dedicated extension point for 
    30     workflow definition deployment.The extension point is called <emphasis 
     30    workflow definition deployment. The extension point is called <emphasis 
    3131    role="bold">definition.</emphasis></para> 
    3232 
    …… 
    3434    application server deployment time (For now, this is the case when the 
    3535    application server is starting up since hot deployment is not yet possible 
    36     using Nuxeo Runtime.at the time of writing this document).It means this 
     36    using Nuxeo Runtime at the time of writing this document).It means this 
    3737    way of deploying workflow definition is not suitable for all cases. See 
    3838    the next subsections for other ways of deploying workflow 
    3939    definitions.</para> 
    4040 
    41     <para>Below is an example of a jpdl workflow definition contribution for 
     41    <para>Below is an example of a jPDL workflow definition contribution for 
    4242    the jBPM backend. This XML fragment would be defined in a contribution 
    4343    registered as a component in a bundle:</para> 
    …… 
    6060    <itemizedlist> 
    6161      <listitem> 
    62         <para><emphasis role="bold">engineName : </emphasis>name specified for 
     62        <para><emphasis role="bold">engineName:</emphasis> name specified for 
    6363        the target backend at workflow service registration time (see workflow 
    6464        service backend extension point)</para> 
    …… 
    6666 
    6767      <listitem> 
    68         <para><emphasis role="bold">mimetype : </emphasis> mimetype of the 
     68        <para><emphasis role="bold">mimetype:</emphasis> mimetype of the 
    6969        workflow definition. This is especially interesting in case of the 
    70         format is binary. (serialization issue at deployement time)</para> 
     70        format is binary. (serialization issue at deployment time)</para> 
    7171      </listitem> 
    7272 
    7373      <listitem> 
    74         <para><emphasis role="bold">definitionPath : </emphasis> bundle 
    75         relative path of fthe worklow definition to deploy.</para> 
     74        <para><emphasis role="bold">definitionPath:</emphasis> bundle 
     75        relative path of the workklow definition to deploy.</para> 
    7676      </listitem> 
    7777    </itemizedlist> 
    7878 
    79     <para>In this situation here is how would look the tree :</para> 
     79    <para>In this situation here is how would look the tree:</para> 
    8080 
    8181    <para><programlisting>com.company.workflow / 

  • doc/nuxeo-book/trunk/src/docbook/workflow-service/jbpm-plugins.xml

    r29472 r30302  
    1515    <title>Process definition deployment</title> 
    1616 
    17     <para>jBPM comes with a simple servlet allowing one to deploy jpdl process 
    18     definitions and minitor running process instances. (NB: this is not yet 
    19     activated on stock Nuxeo5 instance).</para> 
     17    <para>jBPM comes with a simple servlet allowing one to deploy jPDL process 
     18    definitions and monitor running process instances. (NB: this is not yet 
     19    activated on stock Nuxeo 5 instance).</para> 
    2020  </section> 
    2121