Merge pull request shopware#932 from sandoba/master

Fix typos in 45 files

Author: sushmangupta

concepts/framework/architecture/storefront-concept.md

@@ -56,7 +56,7 @@ Let's have a look at the Storefront's general component structure. When opening
 
 Starting at the top of this list, you will find all Storefront controllers inside the `Controller` directory. As said beforehand, a page is being built inside that controller with the help of the corresponding page loaders, Pages, Pagelets, and events, which you will find in the directories: `Pages`, `Pagelets`, and their sub-directories. Each controller method will also give detailed information about its routing with the help of annotations. The directory `DependencyInjection` includes all dependencies which are used in the specific controllers, whereas the `Event` directory includes route request events, and the `Framework` directory, amongst other things, also includes the Routing, Caching, and furthermore. `Migration` and `Test` obviously include migrations and tests for the Storefront component \(e.g., tests for each Storefront controller\).
 
-As the Storefront theme uses Boostrap, the template structure inside `./Resources` is a derivative of the Bootstrap starter template. Besides using Twig as the templating engine and SASS as the CSS preprocessor, we are also using Webpack for bundling and transpiling purposes. This templating directory structure is considered the best practice. If you are interested in developing your own themes or plugins, this section will give more information.
+As the Storefront theme uses Bootstrap, the template structure inside `./Resources` is a derivative of the Bootstrap starter template. Besides using Twig as the templating engine and SASS as the CSS preprocessor, we are also using Webpack for bundling and transpiling purposes. This templating directory structure is considered the best practice. If you are interested in developing your own themes or plugins, this section will give more information.
 
 ## Composite data handling
 

guides/hosting/infrastructure/elasticsearch/elasticsearch-debugging.md

@@ -73,7 +73,7 @@ bin/console dal:refresh:index --use-queue
 
 ### Messenger consume
 
-`messenger:consume -vv` starts a message consumer working on all tasks. This could be startet *X* times. When using more than 3 message consumers, you will need something like RabbitMq to handle the data.
+`messenger:consume -vv` starts a message consumer working on all tasks. This could be started *X* times. When using more than 3 message consumers, you will need something like RabbitMq to handle the data.
 
 ```bash​
 bin/console messenger:consume -vv

guides/hosting/infrastructure/elasticsearch/elasticsearch-setup.md

@@ -70,7 +70,7 @@ Normally a shard in Elasticsearch can hold at least tens of gigabytes, so you mi
 
 | Variable | Possible values | Description |
 | ---------|-----------------|-------------|
-| `APP_ENV`| `prod` / `dev` | This variable is important if you want to activate the debug mode and see possible errors of Elasticsearch. You have to set the variable to dev for debug mode and prod if you want to use elasticsaerch in a productive system.|
+| `APP_ENV`| `prod` / `dev` | This variable is important if you want to activate the debug mode and see possible errors of Elasticsearch. You have to set the variable to dev for debug mode and prod if you want to use Elasticsearch in a productive system.|
 | `OPENSEARCH_URL`| `localhost:9200` | A comma separated list of Elasticsearch hosts. You can find the possible formats [here](https://www.elastic.co/guide/en/elasticsearch/client/php-api/current/host-config.html#inline-host-config)|
 | `SHOPWARE_ES_INDEXING_ENABLED`| `0` / `1` |  This variable activates the indexing to Elasticsearch|
 | `SHOPWARE_ES_ENABLED`| `0` / `1` | This variable activates the usage of Elasticsearch for your shop|
@@ -144,7 +144,7 @@ For a reindex of the whole shop, you can use the command `bin/console dal:refres
 ### Alias creation
 
 Some systems require you to manually execute `bin/console es:create:alias` after the indexing is processed completely.
-Try that command if your index was created fully without errors and you still dont see products in your Storefront.
+Try that command if your index was created fully without errors and you still don't see products in your Storefront.
 
 ### What happens when indexing
 

guides/hosting/infrastructure/reverse-http-cache.md

@@ -118,7 +118,7 @@ sub vcl_recv {
         } elsif (req.http.Accept-Encoding ~ "deflate") {
             set req.http.Accept-Encoding = "deflate";
         } else {
-            # unkown algorithm
+            # unknown algorithm
             unset req.http.Accept-Encoding;
         }
     }
@@ -312,7 +312,7 @@ sub vcl_recv {
         } elsif (req.http.Accept-Encoding ~ "deflate") {
             set req.http.Accept-Encoding = "deflate";
         } else {
-            # unkown algorithm
+            # unknown algorithm
             unset req.http.Accept-Encoding;
         }
     }
@@ -556,7 +556,7 @@ sub vcl_recv {
         } elsif (req.http.Accept-Encoding ~ "deflate") {
             set req.http.Accept-Encoding = "deflate";
         } else {
-            # unkown algorithm
+            # unknown algorithm
             unset req.http.Accept-Encoding;
         }
     }

guides/hosting/installation-updates/composer.md

@@ -1,7 +1,7 @@
 # Versioning and Dependencies
 
 {% hint style="danger" %}
-This setup is no longer the recomended way to manage a Shopware installation. Please refer to our [Flex-guide](../../installation/flex.md#How-do-I-migrate-from-Production-Template-to-Symfony-Flex?) on how to migrate to a symfony flex based setup.
+This setup is no longer the recommended way to manage a Shopware installation. Please refer to our [Flex-guide](../../installation/flex.md#How-do-I-migrate-from-Production-Template-to-Symfony-Flex?) on how to migrate to a symfony flex based setup.
 {% endhint %}
 
 ## Overview
@@ -255,7 +255,7 @@ The following directories should be shared by all app servers:
 │   └── sitemap # rw shared - generated sitemaps
 ├── var
 │   ├── cache # rw local - contains the containers, which contains additional cache directories (twig, translations, etc)
-│   ├── log # a - append only, can be change in the monlog config
+│   ├── log # a - append only, can be change in the monolog config
 
 ro - Readonly after deployment
 rw shared - read and write access, it should be shared across the app servers

guides/installation/community/dockware.md

@@ -12,7 +12,7 @@ Dockware images come in several versions, so you can choose the one which fits y
 | :--- | :--- | :--- |
 | dockware \#play | Launch Shopware in just a couple of seconds locally on your system. Test every functionality and play around while verifying your requirements. | `Production` |
 | dockware \#dev | This is the solution for instant coding. Run Shopware 6, prepare your IDE and immediately start with your own customizations and plugins. Provides Xdebug, watchers or more. | `Production` |
-| dockware \#contribute | This image supports Shopware 6 modification to contribute to the official Shopware 6 Github platform. Contains all dev tools and the already installed demo data. | `developement` |
+| dockware \#contribute | This image supports Shopware 6 modification to contribute to the official Shopware 6 Github platform. Contains all dev tools and the already installed demo data. | `development` |
 | dockware \#essentials | This is a plain Dockware environment without Shopware. | --- |
 | dockware \#flex | This provides a flexible Apache and PHP container for all kinds of Symfony and Shopware projects. It is an image for individualization, e.g., you can manage the Shopware version on your own. | --- |
 

guides/installation/legacy/valet.md

@@ -49,7 +49,7 @@ Additionally, it registers Valet's daemon to launch when your system starts.
 ### Testing your installation
 
 * Make sure `ping something.test` responds from 127.0.0.1.
-* Run `nginx -t` or `sudo nginx -t` and check for any errors. If there is a missing *elastisearch* file, follow the "Missing Elasticsearch stub fix" further below.
+* Run `nginx -t` or `sudo nginx -t` and check for any errors. If there is a missing *elasticsearch* file, follow the "Missing Elasticsearch stub fix" further below.
 
 ### Install Error: "*The process has been signaled with signal 9*"
 

guides/integrations-api/general-concepts/api-versioning.md

@@ -55,7 +55,7 @@ GET /api/test
 sw-expect-packages: shopware/core:~6.4
 ```
 
-This would expect that atleast Shopware with version 6.4 is installed.
+This would expect that at least Shopware with version 6.4 is installed.
 
 ```text
 GET /api/test

guides/integrations-api/general-concepts/search-criteria.md

@@ -103,7 +103,7 @@ The `includes` parameter allows you to restrict the returned fields.
     }
 }
 
-// Reponse
+// Response
 {
     "total": 120,
     "data": [

guides/plugins/apps/flow-builder/add-custom-flow-actions-from-app-system.md

@@ -268,7 +268,7 @@ To get more information on how to create configuration forms, see [Plugin Config
 | time | `<sw-datepicker/>` |
 | colorpicker | `<sw-colorpicker/>` |
 | single-select | `<sw-single-select/>` |
-| ulti-select | `<sw-multi-select/>` |
+| multi-select | `<sw-multi-select/>` |
 
 ## Install the App
 
@@ -281,4 +281,4 @@ bin/console app:install --activate FlowBuilderActionApp
 ## Further steps
 
 * [Flow action example configuration](../../../../resources/references/app-reference/flow-action-reference.md) page
-* [Schema definiton for flow actions (GitHub)](https://github.com/shopware/platform/blob/trunk/src/Core/Framework/App/FlowAction/Schema/flow-action-1.0.xsd)`
+* [Schema definition for flow actions (GitHub)](https://github.com/shopware/platform/blob/trunk/src/Core/Framework/App/FlowAction/Schema/flow-action-1.0.xsd)`