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 7d228d5  WIP.
     new c9ed5fd  Merge remote-tracking branch 'origin/NLPCRAFT-513' into 
NLPCRAFT-513
7d228d5 is described below

commit 7d228d584ba83b920f5a87f09d693cf3c583c55f
Author: skhdl <[email protected]>
AuthorDate: Sat Oct 29 09:27:39 2022 +0400

    WIP.
---
 built-in-builder.html      | 6 +++---
 built-in-token-parser.html | 2 +-
 examples/calculator.html   | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/built-in-builder.html b/built-in-builder.html
index c2d2f04..e06abb5 100644
--- a/built-in-builder.html
+++ b/built-in-builder.html
@@ -81,11 +81,11 @@ id: built-in-builder
         </pre>
         <ul>
             <li>
-                <code>Line 2</code> defines configured <a 
href="StanfordCoreNLP">StanfordCoreNLP</a> class instance.
+                <code>Line 2</code> defines configured 
<code>StanfordCoreNLP</code> class instance.
                 Look at <a href="https://nlp.stanford.edu/";>Stanford NLP</a> 
documentation for more details.
             </li>
             <li>
-                <code>Line 6</code> defines token parser <a 
href="NCStanfordNLPTokenParser">NCStanfordNLPTokenParser</a>, pipeline 
mandatory component.
+                <code>Line 6</code> defines token parser 
<code>NCStanfordNLPTokenParser</code>, pipeline mandatory component.
                 Note that this one instance is used for two places: in 
pipeline definition on <code>line 12</code> and
                 in <a 
href="apis/latest/org/apache/nlpcraft/nlp/parsers/NCSemanticEntityParser.html">NCSemanticEntityParser</a>
 definition on <code>line 14</code>.
             </li>
@@ -102,7 +102,7 @@ id: built-in-builder
                 created on <code>line 7</code> and token parser prepared on 
<code>line 6</code>.
             </li>
             <li>
-                <code>Line 15</code> defines <a 
href="NCStanfordNLPEntityParser">NCStanfordNLPEntityParser</a> based on 
Stanford NER
+                <code>Line 15</code> defines 
<code>NCStanfordNLPEntityParser</code> based on Stanford NER
                 configured for number values detection.
             </li>
             <li>
diff --git a/built-in-token-parser.html b/built-in-token-parser.html
index 267a914..edc4ef7 100644
--- a/built-in-token-parser.html
+++ b/built-in-token-parser.html
@@ -51,7 +51,7 @@ id: built-in-token-parser
     <section id="parser-stanford">
         <h2 class="section-title">Stanford NLP Based Parser<a href="#"><i 
class="top-link fas fa-fw fa-angle-double-up"></i></a></h2>
         <p>
-            There is <a 
href="NCStanfordNLPTokenParser.html">NCStanfordNLPTokenParser</a> 
implementation.
+            There is <code>NCStanfordNLPTokenParser</code> implementation.
 
             This implementation is wrapper on
             <a href="https://nlp.stanford.edu/";>Stanford NLP</a> project 
tokenizer.
diff --git a/examples/calculator.html b/examples/calculator.html
index 027d7aa..7a1ec63 100644
--- a/examples/calculator.html
+++ b/examples/calculator.html
@@ -167,7 +167,7 @@ fa_icon: fa-cube
             <li>
                 <code>Line 14</code> defines model pipeline based on three 
built-in components.
                 <code>Line 21</code> defines Stanford token parser
-                <a href="NCStanfordNLPTokenParser">NCStanfordNLPTokenParser</a>
+                <code>NCStanfordNLPTokenParser</code>
                 (we use Stanford NLP components in this example).
             </li>
             <li>
@@ -177,7 +177,7 @@ fa_icon: fa-cube
             </li>
             <li>
                 <code>Line 23</code> defines entity parser
-                <a 
href="NCStanfordNLPEntityParser">NCStanfordNLPEntityParser</a>
+                <code>NCStanfordNLPEntityParser</code>
                 which allows to find numerics in the text input.
             </li>
             <li>

Reply via email to