diff --git a/docs/03.reference/02.tags/application/tag.md b/docs/03.reference/02.tags/application/tag.md index a539cba7e..1049cf5f0 100644 --- a/docs/03.reference/02.tags/application/tag.md +++ b/docs/03.reference/02.tags/application/tag.md @@ -41,4 +41,4 @@ this.tag.log.log = this.name & ".log"; To verify your current runtime Application configuration use [[function-getapplicationsettings]] -The runtime configuation takes the base server `.CFConfig.json` / admin configuration, overridden by these Application settings. \ No newline at end of file +The runtime configuration takes the base server `.CFConfig.json` / admin configuration, overridden by these Application settings. \ No newline at end of file diff --git a/docs/04.guides/01.getting-started/01.first-steps/page.md b/docs/04.guides/01.getting-started/01.first-steps/page.md index 43c520843..c06bb13db 100644 --- a/docs/04.guides/01.getting-started/01.first-steps/page.md +++ b/docs/04.guides/01.getting-started/01.first-steps/page.md @@ -3,7 +3,7 @@ title: First steps id: getting-started-first-steps --- -Welcome to Lucee, a Free and Open Source, high peformance cfml engine. +Welcome to Lucee, a Free and Open Source, high performance cfml engine. ## Lucee Developer Forum diff --git a/docs/recipes/application-cfc.md b/docs/recipes/application-cfc.md index b618dea52..b8b4bc68e 100644 --- a/docs/recipes/application-cfc.md +++ b/docs/recipes/application-cfc.md @@ -43,9 +43,9 @@ This is only one possible behavior of many, Lucee gives you the possibility in t So, for example, if you only have one Application.cfc in the webroot, define "Root" as setting. -## Configuation Hierarchy +## Configuration Hierarchy -The base Lucee configuation is configured via the `.CFConfig.json` / the Admin. +The base Lucee configuration is configured via the `.CFConfig.json` / the Admin. Each `Application.cfc` can then override / customise these settings per Application. @@ -242,7 +242,7 @@ component { Below you can find an Application.cfc template that may serve as a starting point for your own applications settings with Lucee CFML engine. -When creating an Application.cfc for the first time, you can configure all the settings within the Lucee Server or Web Administrator and use its "Export" tool ( Lucee Adminisitrator => Settings => Export ) to move (by copy and paste) the settings to your Application.cfc. +When creating an Application.cfc for the first time, you can configure all the settings within the Lucee Server or Web Administrator and use its "Export" tool ( Lucee Administrator => Settings => Export ) to move (by copy and paste) the settings to your Application.cfc. ```cfs component displayname="Application" output="false" hint="Handle the application" { diff --git a/docs/recipes/setting-system-properties-and-env-vars.md b/docs/recipes/setting-system-properties-and-env-vars.md index d7a828bf2..0873d0eca 100644 --- a/docs/recipes/setting-system-properties-and-env-vars.md +++ b/docs/recipes/setting-system-properties-and-env-vars.md @@ -32,7 +32,7 @@ Lucee settings are usually configured manually within the Server Administrator f While settings for web-context are also configurable through your web applications Application.cfc (see [[tag-application]]), specific server-context settings can be configured with *Environment Variables* or *System Properties* (since Lucee 5.3). -This allowe Administrators and Developers power to tweak server settings from startup without having to configure in the Server Administrators web interface. +This allows Administrators and Developers power to tweak server settings from startup without having to configure in the Server Administrators web interface. For example, pre-define the extensions to be installed, enable full null support or define charsets for your running Lucee server instance. @@ -99,7 +99,7 @@ Find below a brief overview of available options about where and how to set your CommandBox Limited to the running CommandBox instance - Since CommandBox 4.5 Environment Variables can be set in a file named ".env". You can easily create the .env file by running the command dotenv set from your CommanBox CLI. For more information please see How to set it up CommandBox with .env files and CommandBox Environment Variables + Since CommandBox 4.5 Environment Variables can be set in a file named ".env". You can easily create the .env file by running the command dotenv set from your CommandBox CLI. For more information please see How to set it up CommandBox with .env files and CommandBox Environment Variables diff --git a/docs/recipes/troubleshooting.md b/docs/recipes/troubleshooting.md index 7e0c9c33b..0fb7bb5b6 100644 --- a/docs/recipes/troubleshooting.md +++ b/docs/recipes/troubleshooting.md @@ -61,7 +61,7 @@ Once the initial startup and deployment has got far enough along to have loaded The best first step when debugging a Lucee Server is start Tomcat manually, in a Terminal, as opposed to auto starting or running as service/daemon. -In the `tomcat/bin` directory, there's a bash/batch file called `catalina.sh` or `catalina.bat` which can be run with the run option, i.e `./cataline.sh run` or `catalina run` +In the `tomcat/bin` directory, there's a bash/batch file called `catalina.sh` or `catalina.bat` which can be run with the run option, i.e `./catalina.sh run` or `catalina run` By default, this will show all the `catalina.log` information in the console.