Unify spelling of "colocation" and "colocate" in docs

Author: grebaldi

Documentation/05_Kickstarter.md

@@ -385,12 +385,12 @@ Neos:
 ```
 
 
-### Component file co-location
+### Component file colocation
 
 One great feature of Fusion components is that all files constituting this component are located in the same folder.
 This does not work by default, since Flow packages' classes reside in `Classes`, while presentational components reside in `Resources/Private/Fusion/Presentation`.
 
-To still achieve co-location, two parameters have to be adjusted:
+To still achieve colocation, two parameters have to be adjusted:
 
 #### composer.json
 
@@ -418,7 +418,7 @@ PackageFactory:
         colocate: true
 ```
 
-> **Hint:** It is highly recommended to decide on co-location once at the start of a project.
+> **Hint:** It is highly recommended to decide on colocation once at the start of a project.
 
 ---
 

README.md

@@ -99,10 +99,10 @@ So when using `PackageFactory.AtomicFusion.PresentationObjects`, you need to pay
 
 PresentationObjects require you to write more code than plain AtomicFusion. To remedy that, this package comes with a [scaffolding tool](./Documentation/05_Kickstarter.md) to ease the creation of initial code structures.
 
-Currently, there's also a lot of concepts involved that spread information over the Codebase (`Classes/Presentation/`, `Resources/Private/Fusion/`, `Configuration/`), thus breaking the principle of co-location.
+Currently, there's also a lot of concepts involved that spread information over the Codebase (`Classes/Presentation/`, `Resources/Private/Fusion/`, `Configuration/`), thus breaking the principle of colocation.
 
-In theory, co-location could be achieved by leveraging the `autoload.psr-4` configuration in the composer manifest (see: https://getcomposer.org/doc/04-schema.md#psr-4). However, the viability of this idea has not been proven yet.
-See also the [Kickstarter section](./Documentation/05_Kickstarter.md) on how to achieve co-location.
+In theory, colocation could be achieved by leveraging the `autoload.psr-4` configuration in the composer manifest (see: https://getcomposer.org/doc/04-schema.md#psr-4). However, the viability of this idea has not been proven yet.
+See also the [Kickstarter section](./Documentation/05_Kickstarter.md) on how to achieve colocation.
 
 ### Fusion Interoperation