typo3

Author: MoFoGo

.vscode/settings.json

@@ -7,5 +7,6 @@
   ],
   "cSpell.dictionaries": ["custom", "wordsEn"],
   "cSpell.allowCompoundWords": true,
+  "search.useIgnoreFiles": false,
 
 }

docs/plugins/event-hierarchy.md

@@ -11,7 +11,7 @@ slug: /plugins/EventHierarchy
 
 We have two main events in our `Data Service Generator (DSG)` service. One for the server creation and the other for the admin-ui creation. **These events are running simultaneously, and there is no guarantee which will finish first**
 
-Each of these main events includes other events to create the server’s files and the admin-ui’s files (in our source code it is sometimes referred as and `modules`). 
+Each of these main events includes other events to create the server’s files and the admin-ui files (in our source code it is sometimes referred as and `modules`). 
 
 The following diagram represents the execution order of the events in DSG.
 

docs/plugins/example-plugin.md

@@ -21,7 +21,7 @@ The most straightforward example to illustrate this development workflow is the
 
 - We use Prisma as a ORM and Prisma supports MySQL as a provider - changing the provider on Prisma Schema.
 - We use environment variable for the Prisma schema database’s URL and for the docker-compose values - change the environment variables where needed and their values.
-- Unexpected behaviors: the Prisma’s MySQL provider does not support lists of primitive types
+- Unexpected behaviors: the Prisma MySQL provider does not support lists of primitive types
 
 Translating the above sections to events:
 
@@ -50,7 +50,7 @@ register(): Events {
 
 `CreateServer` : before 
 
-On this event we are taking care of the Prisma’s limitation regrading list of primitives values on MySQL provider.
+On this event we are taking care of the Prisma limitation regrading list of primitives values on MySQL provider.
 
 This is also a good example for a use case where the error should be thrown from the plugin itself.