WIP.
diff --git a/built-in-entity-parser.html b/built-in-entity-parser.html
index b29f9d5..8f0c9a1 100644
--- a/built-in-entity-parser.html
+++ b/built-in-entity-parser.html
@@ -37,18 +37,18 @@
<ul>
<li>
- Wrapper for <a href="https://opennlp.apache.org/">Apache OpenNLP</a> named entities finder which
+ <a href="#parser-opennlp">Wrapper</a> for <a href="https://opennlp.apache.org/">Apache OpenNLP</a> named entities finder which
prepared models support English and some other languages.
</li>
<li>
- Wrapper for <a href="https://nlp.stanford.edu/">Stanford NLP</a> named entities finder which
+ <a href="#parser-stanford">Wrapper</a> for <a href="https://nlp.stanford.edu/">Stanford NLP</a> named entities finder which
prepared models support English and some other languages.
</li>
<li>
- NLP data wrapper implementation. It is not depends on language.
+ NLP data <a href="#parser-nlp">wrapper</a> implementation. It is not depends on language.
</li>
<li>
- Semantic implementation for English language.
+ Semantic <a href="#parser-semantic">implementation</a> for English language.
</li>
</ul>
</section>
diff --git a/built-in-overview.html b/built-in-overview.html
index d301839..2250941 100644
--- a/built-in-overview.html
+++ b/built-in-overview.html
@@ -26,7 +26,7 @@
<h2 class="section-title">Built-in Components Overview<a href="#"><i class="top-link fas fa-fw fa-angle-double-up"></i></a></h2>
<p>
- Model {% scaladoc NCPipeline NCPipeline %} contains
+ <a href="/api-components.html#model-pipeline">Model Pipeline</a> contains
chain of components traits which are responsible for sentence processing.
Some built-in implementations of these traits are described below.
</p>
@@ -38,14 +38,14 @@
{% scaladoc NCTokenParser NCTokenParser %},
{% scaladoc NCTokenEnricher NCTokenEnricher %},
{% scaladoc NCEntityParser NCEntityParser %}.
+ Built-in implementation 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>.
</li>
<li>
- Pipeline components which can't have built-in implementations because their logic are depended on concrete user model:
- {% scaladoc NCTokenValidator NCTokenValidator %},
- {% scaladoc NCEntityEnricher NCEntityEnricher %},
- {% scaladoc NCEntityValidator NCEntityValidator %},
- {% scaladoc NCEntityMapper NCEntityMapper %} and
- {% scaladoc NCVariantFilter NCVariantFilter %}.
+ Other pipeline components can't have built-in implementations
+ because their logic are depended on concrete user model.
</li>
</ul>
diff --git a/custom-components.html b/custom-components.html
index 18c6347..192a43b 100644
--- a/custom-components.html
+++ b/custom-components.html
@@ -26,7 +26,7 @@
<h2 class="section-title">Overview <a href="#"><i class="top-link fas fa-fw fa-angle-double-up"></i></a></h2>
<p>
- NLPCraft provides a numeric of useful built-in components which allow to solve a wide range of tasks
+ NLPCraft provides a numeric of useful <a href="/built-in-overview.html">built-in components</a> which allow to solve a wide range of tasks
without coding.
But you can need to extend provided functionality and develop your own components.
Let's look how to do it and when it can be useful for all kind of components step by step.
