Merge pull request #366 from webforj/324-webforj-capitalization

PR: Corrected Capitalization of "webforj" to "webforJ"

blog/2024-04-08-webforj-v24.00/24.00.md

@@ -13,7 +13,7 @@ import ComponentDemo from '@site/src/components/DocsTools/ComponentDemo';
 
 ![cover image](../../static/release_blog/_images/24.00.png)
 
-webforj version `24.00` is live and available for development. Learn more about what main features and fixes are included in this release.
+webforJ version `24.00` is live and available for development. Learn more about what main features and fixes are included in this release.
 
 <!-- ![cover image](../static/img/webforJ-release-banner.png) -->
 

docs/advanced/web-storage.md

@@ -111,7 +111,7 @@ Local storage stores data with no expiration date. It persists even after the br
 - Not suitable for sensitive data
 - You must manage data yourself, since the browser never automatically deletes it
 
-### Using local storage in webforj
+### Using local storage in webforJ
 
 The following code snippet demonstrates the use of the <JavadocLink type="foundation" location="com/webforj/webstorage/LocalStorage" code='true'>LocalStorage</JavadocLink> object.
 

docs/architecture/architecture.md

@@ -3,9 +3,9 @@ sidebar_position: 5
 title: Client/Server Interaction
 ---
 
-The following section discussed various performance qualities and best practices for webforj, as well as implementation details for the framework.
+The following section discussed various performance qualities and best practices for webforJ, as well as implementation details for the framework.
 
-When creating an application in webforj, the client and the server work together to manipulate data between client and server can be broken down into the broad categories:
+When creating an application in webforJ, the client and the server work together to manipulate data between client and server can be broken down into the broad categories:
 
 ## 1. Server to client
 
@@ -17,7 +17,7 @@ This category covers event traffic, such as a `Button.onClick()` method. For the
 
 ## 3. Server to client to server (round trip)
 
-Round trips are performed when the application queries the client for some dynamic information that cannot be cached on the server. Methods such as `Label.getText()` and `Checkbox.isChecked()` fall into this category. When a webforj application executes a line such as `String title = myLabel.getText()`, it comes to a complete standstill while the server sends that request to the client, then waits for the client to send the response back.
+Round trips are performed when the application queries the client for some dynamic information that cannot be cached on the server. Methods such as `Label.getText()` and `Checkbox.isChecked()` fall into this category. When a webforJ application executes a line such as `String title = myLabel.getText()`, it comes to a complete standstill while the server sends that request to the client, then waits for the client to send the response back.
 
 If the application sends several messages to the client that don't require a response (category 1), followed by a single message that requires a round trip (category 3), the application must wait for the client to process all pending messages, then respond to the final message that requires a response. In some cases, this can add a delay. If that round trip had not been introduced, the client would have been able to continue working through processing those backlogged messages while the application running on the server moved on to new work. 
 
@@ -53,12 +53,12 @@ However, information which cannot be changed by the user can be cached to avoid
 
 ## Loading time 
 
-When the user launches a webforj app, it loads
+When the user launches a webforJ app, it loads
 just a tiny chunk (only about 2.5kB gzip) of JavaScript to bootstrap the session.
 After that, it dynamically downloads individual messages, or chunks of
 JavaScript, on-demand as the application uses the corresponding
 functionality. For example, the server only sends the client the JavaScript
-necessary to build a webforj `Button` once — when the application creates its
+necessary to build a webforJ `Button` once — when the application creates its
 first `Button` component. This results in measurable improvements to the initial
 load time, which results in a better user experience.
 

docs/components/table/table_rendering.md

@@ -6,7 +6,7 @@ slug: rendering
 
 # Rich content and client-side rendering
 
-Tables in webforj are also configurable using the following tools to display rich content within cells. This includes interactive components or formatted data within the table cells.
+Tables in webforJ are also configurable using the following tools to display rich content within cells. This includes interactive components or formatted data within the table cells.
 
 These elements are rendered client-side, meaning the process of generating and displaying rich content is done directly in the browser, using JavaScript only when needed, increasing performance of applications using the `Table`.
 
@@ -86,7 +86,7 @@ The renderer has access to detailed cell, row, and column properties in the clie
 
 While custom renderers can be created, there are multiple pre-configured renderers available for use within a `Table`. The following are available for developers to use out of the box without the need to create a custom renderer:
 
->- `ButtonRenderer` - Renderer for a webforj button.
+>- `ButtonRenderer` - Renderer for a webforJ button.
 >- `NativeButtonRenderer` - Renderer for a native HTML button.
 >- `ElementRenderer` - The base class for all renderers which render an HTML tag **with** content.
 >- `VoidElementRenderer` - The base class for all renderers which render a void element, or an HTML tag **without** content.

docs/introduction/getting-started.md

@@ -3,7 +3,7 @@ title: Getting Started
 sidebar_position: 2
 ---
 
-This article outlines the steps to scaffold a new webforJ app using the webforj archetypes. This archetypes provide a pre-configured project structure and starter code to quickly get a project up and running.
+This article outlines the steps to scaffold a new webforJ app using the webforJ archetypes. This archetypes provide a pre-configured project structure and starter code to quickly get a project up and running.
 
 :::tip Prerequisites
 Before you begin, ensure you have read about the necessary [prerequisites](./prerequisites) for setting up and using webforJ.