docs: fix typos in docs pages and CLI help strings

Correct misspellings across the documentation (overridden, specified,
occurred, container, continuously, permanently, successfully, Daemon,
Kubernetes, etc.) and remove a doubled "and" in the README.

Two of the typos originate in Go command definitions and are fixed at
the source so the generated CLI reference stays in sync:

- cmd/init.go: "intialization" in the --context flag help, and
  "specfied" in the devspace.yaml template written by `devspace init`
- cmd/logs.go: "attachs" in the `devspace logs` short description

Author: toyeshhm

README.md

@@ -87,7 +87,7 @@ Instead of rebuilding images and redeploying containers, DevSpace allows you to
 <br>
 
 Deploying and debugging services with Kubernetes requires a lot of knowledge and forces you to repeatedly run commands like `kubectl get pod` and copy pod ids back and forth. Stop wasting time and let DevSpace automate the tedious parts of working with Kubernetes:
-- DevSpace lets you build multiple images in parallel, tag them automatically and and deploy your entire application (including its dependencies) with just a single command
+- DevSpace lets you build multiple images in parallel, tag them automatically and deploy your entire application (including its dependencies) with just a single command
 - Let DevSpace automatically start port-fowarding and log streaming, so you don't have to constantly copy and paste pod ids or run 10 commands to get everything started.
 
 <br>

cmd/init.go

@@ -96,7 +96,7 @@ folder. Creates a devspace.yaml as a starting point.
 	}
 
 	initCmd.Flags().BoolVarP(&cmd.Reconfigure, "reconfigure", "r", false, "Change existing configuration")
-	initCmd.Flags().StringVar(&cmd.Context, "context", "", "Context path to use for intialization")
+	initCmd.Flags().StringVar(&cmd.Context, "context", "", "Context path to use for initialization")
 	initCmd.Flags().StringVar(&cmd.Dockerfile, "dockerfile", helper.DefaultDockerfilePath, "Dockerfile to use for initialization")
 	initCmd.Flags().StringVar(&cmd.Provider, "provider", "", "The cloud provider to use")
 
@@ -508,7 +508,7 @@ echo 'Anyone using this project can invoke it via "devspace run migrate-db"'`,
 	config.Pipelines["dev"] = &latest.Pipeline{
 		Run: `run_dependencies --all       # 1. Deploy any projects this project needs (see "dependencies")
 ensure_pull_secrets --all    # 2. Ensure pull secrets
-create_deployments --all     # 3. Deploy Helm charts and manifests specfied as "deployments"
+create_deployments --all     # 3. Deploy Helm charts and manifests specified as "deployments"
 start_dev ` + imageName + `                # 4. Start dev mode "` + imageName + `" (see "dev" section)`,
 	}
 
@@ -517,7 +517,7 @@ start_dev ` + imageName + `                # 4. Start dev mode "` + imageName +
 		Run: `run_dependencies --all                            # 1. Deploy any projects this project needs (see "dependencies")
 ensure_pull_secrets --all                         # 2. Ensure pull secrets
 build_images --all -t $(git describe --always)    # 3. Build, tag (git commit hash) and push all images (see "images")
-create_deployments --all                          # 4. Deploy Helm charts and manifests specfied as "deployments"`,
+create_deployments --all                          # 4. Deploy Helm charts and manifests specified as "deployments"`,
 	}
 
 	// Save config

cmd/logs.go

@@ -50,7 +50,7 @@ func NewLogsCmd(f factory.Factory, globalFlags *flags.GlobalFlags) *cobra.Comman
 #######################################################
 #################### devspace logs ####################
 #######################################################
-Prints the last log of a pod container and attachs 
+Prints the last log of a pod container and attaches 
 to it
 
 Example:

docs/pages/_partials/config-dependencies.mdx

@@ -18,7 +18,7 @@ dependencies:                       # struct[]  | Array of dependencies (other p
     ports: false                    # bool      | Reuse dev.ports config from the dependency
     sync: false                     # bool      | Reuse dev.sync config from the dependency
   overwriteVars: true               # bool      | If not defined or true, will overwrite values of variables with the same name in the dependency
-  vars:                             # struct[]  | Variables in the dependency config that should be overriden with the specified values 
+  vars:                             # struct[]  | Variables in the dependency config that should be overridden with the specified values 
   - name: NAME
     value: value
   disableProfileActivation: true    # bool      | If true will ignore profile activations for this dependency

docs/pages/_partials/dependency-vars.mdx

@@ -1,4 +1,4 @@
-The `vars` option expects an array of objects with name and value of variables defined in the `devspace.yaml` of this dependency. When configuring this option, the variables will be overriden similar to passing variables via the `--var` flag to devspace.
+The `vars` option expects an array of objects with name and value of variables defined in the `devspace.yaml` of this dependency. When configuring this option, the variables will be overridden similar to passing variables via the `--var` flag to devspace.
 It is also useful to deploy the same dependency multiple times with just small adjustments.
 
 #### Example: Override Config Vars for Dependency

docs/pages/_partials/workflow-open-links.mdx

@@ -1,4 +1,4 @@
 
-1. DevSpace starts to periodically send `HTTP GET` requests to the URLs provideded via `dev.*.open[*].url`.
+1. DevSpace starts to periodically send `HTTP GET` requests to the URLs provided via `dev.*.open[*].url`.
 2. As soon as the first HTTP response has a status code which is neither 502 (Bad Gateway) nor 503 (Service Unavailable), DevSpace assumes that the application is now started, stops sending any further requests and opens the provided URL in the browser.
 3. If the URL is still returning status code 502 or 503 after 4min, DevSpace will stop trying to open it. To not disturb the log streaming or the interactive terminal session, DevSpace will not show an error when hitting the 4min timeout.

docs/pages/cli/devspace_init.md

@@ -26,7 +26,7 @@ folder. Creates a devspace.yaml as a starting point.
 ## Flags
 
 ```
-      --context string      Context path to use for intialization
+      --context string      Context path to use for initialization
       --dockerfile string   Dockerfile to use for initialization (default "./Dockerfile")
   -h, --help                help for init
       --provider string     The cloud provider to use

docs/pages/cli/devspace_logs.md

@@ -17,7 +17,7 @@ devspace logs [flags]
 #######################################################
 #################### devspace logs ####################
 #######################################################
-Prints the last log of a pod container and attachs 
+Prints the last log of a pod container and attaches 
 to it
 
 Example:

docs/pages/configuration/dev/connections/file-sync.mdx

@@ -270,7 +270,7 @@ dev:
 The `initialSync` option expects a string with an initial sync strategy. The following strategies are available:
 
 `mirrorLocal` mirrors the local filesystem inside the container (default)  
-  1. deletes all files inside the conainer that are not existing on the local filesystem
+  1. deletes all files inside the container that are not existing on the local filesystem
   2. uploads all files which are existing on the local filesystem but are missing within the container
   3. resolves all file conflicts (different content on local filesystem than in inside the container) by preferring the file on the local filesystem (i.e. all files in the container will be replaced if they are different from on the local filesystem)
 
@@ -438,7 +438,7 @@ DevSpace establishes a bi-directional code synchronization between the specified
 The algorithm roughly works like this:
 
 1. Inject a small helper binary via `kubectl cp` into the target container
-2. Run initial sync accoring to the [`initialSync` config option](#initial-sync)
+2. Run initial sync according to the [`initialSync` config option](#initial-sync)
 3. Watch for file changes on both sides (local and remote) and sync them according to the [sync path mappings](#sync-path-mapping)
 4. After every sync process, [restart the container](#onuploadrestartcontainer) or run other custom [post-sync commands](#post-sync-commands) (optional)
 

docs/pages/configuration/dev/connections/terminal.mdx

@@ -100,7 +100,7 @@ dev:
       lastLines: 100
 ```
 
-DevSpace will continously check what pods match the given selectors and start or end log streaming accordingly.
+DevSpace will continuously check what pods match the given selectors and start or end log streaming accordingly.
 
 
 ## Config Reference