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

aradzinski 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 36f2ae8  WIP
36f2ae8 is described below

commit 36f2ae8dba38bd6fc5617b956e3d048ebf0addee
Author: Aaron Radzinski <[email protected]>
AuthorDate: Sat Nov 26 12:21:25 2022 -0800

    WIP
---
 README.md              |  2 +-
 short-term-memory.html | 14 +++++---------
 2 files changed, 6 insertions(+), 10 deletions(-)

diff --git a/README.md b/README.md
index 10fa136..202050d 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ NLPCraft is free and easy to use, it securely works with any 
private data source
 lock-in:
 
  * View & run 
[examples](https://github.com/apache/incubator-nlpcraft/tree/master/nlpcraft-examples)
- * Latest 
[Javadoc](https://github.com/apache/incubator-nlpcraft/apis/latest/index.html) 
and [REST APIs](https://nlpcraft.apache.org/using-rest.html)
+ * Latest 
[Scaladoc](https://github.com/apache/incubator-nlpcraft/apis/latest/index.html)
  * Download & Maven/Grape/Gradle/SBT 
[instructions](https://nlpcraft.apache.org/download.html)
  * File a bug or improvement in 
[JIRA](https://issues.apache.org/jira/projects/NLPCRAFT)
  * Post a question at [Stack 
Overflow](https://stackoverflow.com/questions/ask) using <code>nlpcraft</code> 
tag
diff --git a/short-term-memory.html b/short-term-memory.html
index e349c31..f49d5e0 100644
--- a/short-term-memory.html
+++ b/short-term-memory.html
@@ -111,8 +111,7 @@ id: short_term_memory
             Conversation management implementation is also smart enough to 
clear STM after certain
             period of time, i.e. it “forgets” the conversational context after 
few minutes of inactivity.
             Note also that conversational context can also be cleared 
explicitly
-            via <a 
href="https://app.swaggerhub.com/apis-docs/Apache-NLPCraft/apache-nlpcraft/{{site.latest_version}}";
 target="swaggerhub">REST API</a>
-            or from the <a class="not-code" target="javadoc" 
href="/apis/latest/org/apache/nlpcraft/NCConversation.html">code</a>.
+            using {% scaladoc NCConversation %}.
         </p>
         <p>
             To understand the algorithm behind the STM management let's back 
up a few steps...
@@ -263,13 +262,11 @@ id: short_term_memory
             Despite somewhat obvious logic the implementation of context 
switch is not an exact science. Sometimes, you
             can have a "soft" context switch where you don't change the topic 
of the conversation 100% but yet sufficiently
             enough to forget at least some parts of the previously collected 
context. NLPCraft has a built-in algorithm
-            to detect the hard switch in the conversation. It also exposes
-            <a class="not-code" target="javadoc" 
href="/apis/latest/org/apache/nlpcraft/NCConversation.html">API</a> to perform 
a selective reset on the
-            conversation in case of "soft" switch.
+            to detect the hard switch in the conversation. You can also use {% 
scaladoc NCConversation %} to perform a
+            selective reset on the conversation in case of "soft" switch.
         </p>
         <p>
-            See <a class="javadoc" 
href="/apis/latest/org/apache/nlpcraft/NCConversation.html">NCConversion</a> 
interface
-            for API details for STM management.
+            See {% scaladoc NCConversation %} interface for API details for 
STM management.
         </p>
     </section>
     <section id="override">
@@ -452,8 +449,7 @@ id: short_term_memory
         </p>
         <p>
             In NLPCraft you can also explicitly reset conversation context 
through
-            <a class="not-code" target="javadoc" 
href="/apis/latest/org/apache/nlpcraft/NCConversation.html">API</a>
-            or by switching the model on the request.
+            {% scaladoc NCConversation %} interface or by switching the model 
on the request.
         </p>
     </section>
 </div>

Reply via email to