Merge pull request #39 from Codeplain-ai/docs/grammatical-mistakes

Corrected Plain to ***plain spelling

Author: kaja-s

README.md

@@ -17,7 +17,7 @@ Schematic overview of the Codeplain's code generation service
 
 An example application in ***plain
 
-<img src="resources/plain_example.png" width="50%" height="50%">
+<img src="resources/plain_example.png" width="70%" height="70%">
 
 
 ## Getting started
@@ -87,7 +87,7 @@ After completing the installation steps above, you can immediately test the syst
 ### Documentation
 
 - For more details on the ***plain format, see the [***plain language specification](docs/plain_language_specification.md).
-- For step-by-step instructions for creating your first ***plain project see the [Kickstart your plain project](docs/starting_a_plain_project_from_scratch.md).
+- For step-by-step instructions for creating your first ***plain project see the [Kickstart your ***plain project](docs/starting_a_plain_project_from_scratch.md).
 - For complete CLI documentation and usage examples, see [plain2code CLI documentation](docs/plain2code_cli.md).
 
 

docs/plain_language_specification.md

@@ -115,7 +115,7 @@ Definitions are the mechanism for definining data structures in ***plain. Here's
 
 The `***Non-Functional Requirements:***` specification is a list of instructions that steer software code implementation and provide details of execution environment.
 
-Here's an example of a simple instruction specifying only that the Plain specification should be rendered to Python software code.
+Here's an example of a simple instruction specifying only that the ***plain specification should be rendered to Python software code.
 
 ```plain
 - :Implementation: should be in Python.
@@ -149,7 +149,7 @@ Each functional requirement must be limited in complexity. For example, for the
 - :App: should implement a task manager application.
 ```
 
-the renderer of Plain source to software code should respond with
+the renderer of ***plain source to software code should respond with
 
 ```
 Functional requirement too complex!
@@ -219,18 +219,18 @@ Lines starting with `>` are ignored when rendering software code.
 
 ## Template System
 
-Plain supports template inclusion using the `{% include %}` syntax, which allows you to use predefined templates in your specifications.
+***plain supports template inclusion using the `{% include %}` syntax, which allows you to use predefined templates in your specifications.
 
 ```plain
 {% include "python-console-app-template.plain", main_executable_file_name: "my_app.py" %}
 ```
 Predefined templates are available for Go console apps, Python console apps, and TypeScript React apps in the [standard template library](../standard_template_library/). You can also create your own custom templates.
 
-The template system enables code reuse and standardization across Plain projects.
+The template system enables code reuse and standardization across ***plain projects.
 
 ## Linked Resources
 
-If you include a link using the markdown syntax, the linked resource will be passed along with the Plain specification to the renderer.
+If you include a link using the markdown syntax, the linked resource will be passed along with the ***plain specification to the renderer.
 
 Here's an example of a linked resource (see Task manager example application for the full specification).
 
@@ -239,12 +239,12 @@ Here's an example of a linked resource (see Task manager example application for
 ```
 
 **Important Notes:**
-- Only links to files in the same folder (and its subfolders) as the Plain specification are supported. Links to external resources are not supported.
-- File paths are resolved relative to the location of the Plain specification file.
+- Only links to files in the same folder (and its subfolders) as the ***plain specification are supported. Links to external resources are not supported.
+- File paths are resolved relative to the location of the ***plain specification file.
 - All types are supported, except binary files.
 
 ## Liquid templates
 
-Plain supports Liquid templates. Liquid is an open-source template language created by Shopify (https://shopify.github.io/liquid/).
+***plain supports Liquid templates. Liquid is an open-source template language created by Shopify (https://shopify.github.io/liquid/).
 
 For a sample use of Liquid templates see [example-saas-connectors](https://github.com/Codeplain-ai/example-saas-connectors) repository.

docs/starting_a_plain_project_from_scratch.md

@@ -1,6 +1,6 @@
-# How to Start a New Plain Project from Scratch
+# How to Start a New ***plain Project from Scratch
 
-This guide will walk you through creating your first Plain project from scratch.
+This guide will walk you through creating your first ***plain project from scratch.
 It assumes you have already:
 
 ✅ Met all [prerequisites](../README.md#prerequisites),
@@ -9,11 +9,11 @@ It assumes you have already:
 
 If you haven't done so yet, please refer to [README](../README.md).
 
-After following this guide, you'll be equipped to turn your ideas into working code with Plain.
+After following this guide, you'll be equipped to turn your ideas into working code with ***plain.
 
 ## Project Structure Overview
 
-Every Plain project follows this basic structure:
+Every ***plain project follows this basic structure:
 
 ```
 my-new-project/
@@ -29,7 +29,7 @@ In this guide we will cover how to create each of these step by step.
 
 ## 1. Define Your .plain File
 
-Create a `.plain` file. The following example shows how to specify the array sorting problem. For more details, see [Plain language specifications](plain_language_specification.md).
+Create a `.plain` file. The following example shows how to specify the array sorting problem. For more details, see [***plain language specifications](plain_language_specification.md).
 
 **Example: `array_sorting.plain`**
 ```plain
@@ -74,7 +74,7 @@ conformance-tests-script: ./run_conformance_tests_python.sh
 verbose: true
 
 ```
-- Specify the test scripts so that Plain knows how to run unit and conformance tests.
+- Specify the test scripts so that ***plain knows how to run unit and conformance tests.
 - Indicate whether to display detailed output during code generation like shown in output control. 
 - For additional options and advanced configuration, see the [plain2code CLI documentation](plain2code_cli.md).