corrected webforJ spelling.

Author: EHandtkeBasis

docs/docs/configuration/gradle.md

@@ -1,16 +1,16 @@
 ---
-title: Converting a WebforJ Maven Project to Gradle
+title: Converting a webforJ Maven Project to Gradle
 sidebar_position: 3
-description: Learn how to migrate a WebforJ project from Maven to Gradle using Groovy Domain Specific Language.
+description: Learn how to migrate a webforJ project from Maven to Gradle using Groovy Domain Specific Language.
 ---
 
-# Converting a WebforJ maven project to gradle
+# Converting a webforJ maven project to gradle
 
-If you're working with a WebforJ project and looking to switch from Maven to Gradle, this guide walks you through the key changes required to translate a typical `pom.xml` file into a working `build.gradle` script using Groovy Domain Specific Language. The examples are tailored specifically for WebforJ setups, including Jetty integration, WAR packaging, and profile-based configuration.
+If you're working with a webforJ project and looking to switch from Maven to Gradle, this guide walks you through the key changes required to translate a typical `pom.xml` file into a working `build.gradle` script using Groovy Domain Specific Language. The examples are tailored specifically for webforJ setups, including Jetty integration, WAR packaging, and profile-based configuration.
 
 ## 1. Apply required plugins
 
-WebforJ typically packages the app as a WAR file and runs using Jetty. Enable the following plugins:
+webforJ typically packages the app as a WAR file and runs using Jetty. Enable the following plugins:
 
 ```groovy
 plugins {