@@ -24,7 +24,7 @@ import { ILlmApplicationOfValidate } from "./module";
24
24
*
25
25
* By the way, there can be some parameters (or their nested properties) which must be
26
26
* composed by human, not by LLM. File uploading feature or some sensitive information
27
- * like secrety key (password) are the examples. In that case, you can separate the
27
+ * like security keys (password) are the examples. In that case, you can separate the
28
28
* function parameters to both LLM and human sides by configuring the
29
29
* {@link ILlmApplicationOfValidate.IOptions.separate} property. The separated parameters
30
30
* are assigned to the {@link ILlmFunctionOfValidate.separated} property.
@@ -85,7 +85,7 @@ export function applicationOfValidate(
85
85
*
86
86
* By the way, there can be some parameters (or their nested properties) which must be
87
87
* composed by human, not by LLM. File uploading feature or some sensitive information
88
- * like secrety key (password) are the examples. In that case, you can separate the
88
+ * like security keys (password) are the examples. In that case, you can separate the
89
89
* function parameters to both LLM and human sides by configuring the
90
90
* {@link ILlmApplicationOfValidate.IOptions.separate} property. The separated parameters
91
91
* are assigned to the {@link ILlmFunctionOfValidate.separated} property.
@@ -155,7 +155,7 @@ export function applicationOfValidate(): never {
155
155
*
156
156
* By the way, there can be some parameters (or their nested properties) which must be
157
157
* composed by human, not by LLM. File uploading feature or some sensitive information
158
- * like secrety key (password) are the examples. In that case, you can separate the
158
+ * like security keys (password) are the examples. In that case, you can separate the
159
159
* function parameters to both LLM and human sides by configuring the
160
160
* {@link ILlmApplication.IOptions.separate} property. The separated parameters are
161
161
* assigned to the {@link ILlmFunction.separated} property.
@@ -210,7 +210,7 @@ export function application(
210
210
*
211
211
* By the way, there can be some parameters (or their nested properties) which must be
212
212
* composed by human, not by LLM. File uploading feature or some sensitive information
213
- * like secrety key (password) are the examples. In that case, you can separate the
213
+ * like security keys (password) are the examples. In that case, you can separate the
214
214
* function parameters to both LLM and human sides by configuring the
215
215
* {@link ILlmApplication.IOptions.separate} property. The separated parameters are
216
216
* assigned to the {@link ILlmFunction.separated} property.
@@ -385,8 +385,8 @@ export function parameters(): never {
385
385
*
386
386
* > **What LLM function calling is?
387
387
* >
388
- * > LLM (Large Language Model) selects propert function and fill the arguments,
389
- * > but actuall function call execution is not by LLM, but by you.
388
+ * > LLM (Large Language Model) selects property function and fill the arguments,
389
+ * > but actual function call execution is not by LLM, but by you.
390
390
* >
391
391
* > In nowadays, most LLM (Large Language Model) like OpenAI are supporting
392
392
* > "function calling" feature. The "function calling" means that LLM automatically selects
@@ -432,8 +432,8 @@ export function schema(): never;
432
432
*
433
433
* > **What LLM function calling is?
434
434
* >
435
- * > LLM (Large Language Model) selects propert function and fill the arguments,
436
- * > but actuall function call execution is not by LLM, but by you.
435
+ * > LLM (Large Language Model) selects property function and fill the arguments,
436
+ * > but actual function call execution is not by LLM, but by you.
437
437
* >
438
438
* > In nowadays, most LLM (Large Language Model) like OpenAI are supporting
439
439
* > "function calling" feature. The "function calling" means that LLM automatically selects
0 commit comments