spelling

Author: dzmitry-lahoda

src/api/pc_api.go

@@ -1,11 +1,12 @@
 package api
 
 import (
-	"github.com/f1bonacc1/process-compose/src/types"
 	"net/http"
 	"strconv"
 	"sync"
 
+	"github.com/f1bonacc1/process-compose/src/types"
+
 	"github.com/f1bonacc1/process-compose/src/app"
 	"github.com/gin-gonic/gin"
 )
@@ -372,7 +373,7 @@ func (api *PcApi) UpdateProject(c *gin.Context) {
 
 // @Schemes
 // @Id				UpdateProcess
-// @Description	Update porcess
+// @Description	Update process
 // @Tags			Process
 // @Summary		Updates process configuration
 // @Produce		json

src/app/system_test.go

@@ -170,8 +170,8 @@ func TestSystem_TestComposeCircular(t *testing.T) {
 		_, err := loader.Load(&loader.LoaderOptions{
 			FileNames: []string{fixture1},
 		})
-		if err == nil {
-			t.Error("should fail on cirlcular dependency")
+			if err == nil {
+				t.Error("should fail on circular dependency")
 			return
 		}
 

src/docs/docs.go

@@ -42,7 +42,7 @@ const docTemplate = `{
         },
         "/process": {
             "post": {
-                "description": "Update porcess",
+                "description": "Update process",
                 "produces": [
                     "application/json"
                 ],

src/docs/swagger.json

@@ -512,7 +512,7 @@
         },
         "/process": {
             "post": {
-                "description": "Update porcess",
+                "description": "Update process",
                 "operationId": "UpdateProcess",
                 "responses": {
                     "200": {

src/docs/swagger.yaml

@@ -348,7 +348,7 @@ paths:
                 - Liveness
     /process:
         post:
-            description: Update porcess
+            description: Update process
             operationId: UpdateProcess
             responses:
                 "200":

www/docs/configuration.md

@@ -447,7 +447,7 @@ processes:
     namespace: debug # if not defined 'default' namespace is automatically assigned to each process
 ```
 
-Note: By default `process-compose` will start process from all the configured namespaces. To start a sub set of the configured namespaces (`ns1`, `ns2`, `ns3`):
+Note: By default `process-compose` will start processes from all the configured namespaces. To start a subset of the configured namespaces (`ns1`, `ns2`, `ns3`):
 
 ```shell
 process-compose -n ns1 -n ns3
@@ -457,7 +457,7 @@ process-compose -n ns1 -n ns3
 ## Misc
 
 #### Strict Configuration Validation
-To avoid minor `proces-compose.yaml` configuration errors and typos it is recommended to enable `is_strict` flag:
+To avoid minor `process-compose.yaml` configuration errors and typos it is recommended to enable `is_strict` flag:
 
 ```yaml hl_lines="2 5"
 version: "0.5"

www/docs/merge.md

@@ -1,4 +1,4 @@
-Using multiple `process-compose` files lets you to customize a `process-compose` application for different environments or different workflows.
+Using multiple `process-compose` files lets you customize a `process-compose` application for different environments or different workflows.
 
 ### Understanding multiple Compose files
 
@@ -272,4 +272,4 @@ Both `disabled` (boolean) and `is_disabled` (string) can coexist, but `is_disabl
 
 - For **standard configuration** within a single file or when not dealing with complex override scenarios to *enable* a process, you can continue using the boolean `disabled` field (`disabled: true` or `disabled: false`).
 - When **using override files** specifically to *enable* a process that might be disabled in a base file, use `is_disabled: "false"` in the override file for guaranteed results.
-- You can also use `is_disabled: "true"` in override files if you prefer consistency, although `disabled: true` generally works reliably for disabling.
+- You can also use `is_disabled: "true"` in override files if you prefer consistency, although `disabled: true` generally works reliably for disabling.