From b0e42ddced78aa66a23e466a2f369e183a57c18e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C2=B7=F0=90=91=91=F0=90=91=B4=F0=90=91=95=F0=90=91=91?= =?UTF-8?q?=F0=90=91=A9=F0=90=91=A4?= Date: Sat, 19 Jul 2025 11:02:33 +0700 Subject: [PATCH] docs/factor: fixup Factor docs referencing correct vocab root name --- doc/languages-frameworks/factor.section.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/languages-frameworks/factor.section.md b/doc/languages-frameworks/factor.section.md index 0d67eede4d34..1bedfbc9e7bc 100644 --- a/doc/languages-frameworks/factor.section.md +++ b/doc/languages-frameworks/factor.section.md @@ -65,7 +65,7 @@ It also understands the following special attributes: - `vocabRoot` is the vocabulary root to install the vocabulary under. Defaults to `extra`. Unless you know what you are doing, do not change it. - Other readily understood vocabulary roots are `core` and `base`, which allow you to modify the default Factor runtime environment with an external package. + Other readily understood vocabulary roots are `core` and `basis`, which allow you to modify the default Factor runtime environment with an external package. - `extraLibs`, `extraVocabs`, `extraPaths` have the same meaning as for [applications](#ssec-factor-applications). They have no immediate effect and are just passed through. When building factor-lang packages and Factor applications that use this respective vocabulary, these variables are evaluated and their paths added to the runtime environment.