This is an automated email from the ASF dual-hosted git repository.

sergeykamov pushed a commit to branch NLPCRAFT-513
in repository https://gitbox.apache.org/repos/asf/incubator-nlpcraft-website.git


The following commit(s) were added to refs/heads/NLPCRAFT-513 by this push:
     new 3fd637a  WIP.
3fd637a is described below

commit 3fd637a5fcb01a3949481795073df273abeb01c0
Author: skhdl <[email protected]>
AuthorDate: Tue Nov 1 19:23:46 2022 +0400

    WIP.
---
 built-in-overview.html     | 20 ++++++++------------
 built-in-token-parser.html |  6 +++---
 2 files changed, 11 insertions(+), 15 deletions(-)

diff --git a/built-in-overview.html b/built-in-overview.html
index e205a12..8eebc84 100644
--- a/built-in-overview.html
+++ b/built-in-overview.html
@@ -35,22 +35,18 @@ id: built-in-overview
         <ul>
             <li>
                 Pipeline components
-                <code>token parser</code>,
-                <code>token enricher</code> and
-                <code>entity parser</code>
-                have built-in implementations and can have broad range of uses.
-                Built-in implementations of them are described in related 
sections:
                 <a href="/built-in-token-parser.html">Token Parsers</a>,
-                <a href="/built-in-token-enricher.html">Token Enrichers</a>,
-                <a href="/built-in-entity-parser.html">Entity Parsers</a>.
+                <a href="/built-in-token-enricher.html">Token Enrichers</a> and
+                <a href="/built-in-entity-parser.html">Entity Parsers</a>
+                have built-in implementations and can have broad range of uses.
             </li>
             <li>
                 Other pipeline components:
-                <code>token validator</code>,
-                <code>entity enricher</code>,
-                <code>entity mapper</code>,
-                <code>entity validator</code> and
-                <code>variant filter</code>
+                <code>Token Validators</code>,
+                <code>Entity Enrichers</code>,
+                <code>Entity Mappers</code>,
+                <code>Entity Validators</code> and
+                <code>Variant Filters</code>
                 can't have built-in implementations
                 because their logic are depended on concrete user model.
             </li>
diff --git a/built-in-token-parser.html b/built-in-token-parser.html
index 0f1eb27..cb684dc 100644
--- a/built-in-token-parser.html
+++ b/built-in-token-parser.html
@@ -29,9 +29,9 @@ id: built-in-token-parser
             {% scaladoc NCTokenParser NCTokenParser %}
             component implementation should parse user input plain text and 
split this text
             into <code>tokens</code> list.
-
-            NLPCraft provides two English language token parser 
implementations.
-
+            NLPCraft provides two English language token parser 
implementations:
+            <a href="#parser-opennlp">Apache OpenNLP Based Parser</a> and
+            <a href="#parser-stanford">Stanford NLP Based Parser</a>.
             Also, project contains examples for <a 
href="examples/light_switch_fr.html">French</a> and
             <a href="examples/light_switch_ru.html">Russia</a> languages token 
parser implementations.
         </p>

Reply via email to