Update readme.md

readme.md

@@ -15,7 +15,7 @@ AllSpice actions is the building block of Continuous Integration and Continous D
 
 ## How they work?
 
-AllSpice actions work in a simple way, similar to other CI/CD solutions for software like Gitlab CI/CD or Github Actions. It all starts with an event within you repo (Eg. a new design review) that triggers a runner to execute a specific set of tasks. The defined groupd of tasks are called workflows and each task is absically a script that does something for you. You can use custom scripts or pre made ones from the allspice library. You can also have as many tasks as you want in a workflow and as many workflows as you want in your repo. Below you can see a simplified diagram of how an AllSpice Action works. For more info you can go to our actions documentation.
+AllSpice Actions operate similarly to other CI/CD solutions like GitLab CI/CD or GitHub Actions. The process begins with an event within your repository (e.g., a new design review) that triggers a runner to execute a specific set of tasks. These tasks are grouped into workflows, where each task is essentially a script performing a specific function. You can use custom scripts or pre-made ones from the AllSpice library. Additionally, you can include as many tasks as needed in a workflow and have multiple workflows in your repository. Below is a simplified diagram of how an AllSpice Action works. For more information, please refer to our Actions documentation.
 
 <div align="left">
 	<img src="./images/Actions-workflows.png">