(docs): Adding some content adjustments to the file so that things are more clear for the plugin section.

Author: dericksozo

docs/getting-started/plugins.md

@@ -10,7 +10,8 @@ pagination_prev: getting-started/community-plugins
 
 Amplication uses _Plugins_ to extend the functionality of your generated service. These software additions allow developers to customize the default behavior of [Amplication's code generation process](/plugins/plugin-architecture/), providing hooks into various stages of service creation.
 
-Amplication offers a wide range of community-created plugins that are open-source and available on GitHub. You also have the flexibility to develop your own [custom plugins](/plugins/overview/) so you can tailor your generated service to meet your exact requirements.
+Amplication offers a wide range of community plugins that are open-source and available on GitHub.
+You can also [develop your own private plugins](/private-plugins/) and [community plugins](/plugins/overview/) to extend Amplication's functionality and have it meet your exact requirements.
 
 You can enable certain plugins when you first create your service.
 For example, if you choose MySQL as your database, the _MySQL DB_ plugin will be enabled.

docs/plugins/plugin-architecture.md

@@ -15,7 +15,16 @@ The `pluginWrapper` function is invoked with the following arguments:
 - **event** - the name of event we want to capture, and change something in the triggered process.
 - **args** - the original parameters of the DSG function. These are likely to be used as the parameters of the event, for the plugin developer to have access to these params and manipulate the returned value of the function.
 
-For the purpose of this architecture overview, remember that every event has before and after property (which is a function), representing the event's lifecycle in which you can intervene (before the emission of the event and after the emission of the event). For more information about `before` and `after` event see [Before and After Lifecycle Functions](docs\plugins\before-after.md)
+## Event Lifecycle
+
+Each plugin event supports two execution points:
+
+- `before`: Executes before the main event processing
+- `after`: Executes after the main event processing
+
+These lifecycle hooks allow precise control over the code generation process.
+
+For more information about `before` and `after` event see [Before and After Lifecycle Functions](docs\plugins\before-after.md)
 
 When the `pluginWrapper` function is invoked, it checks whether the event argument that was passed has a `before` or `after` property. If so, it invokes other functions that are responsible for calculating the final behavior when this event is emitted, or in other words, the outcome of the function that this event is responsible to execute.
 

docs/plugins/plugindev-overview.md

@@ -9,7 +9,8 @@ pagination_prev: plugins/event-hierarchy
 
 # Plugin Development Overview
 
-A plugin is a custom code that extends Amplication developer platform with new features. The features incorporated can be generic, useful to a wide variety of users, or can be very specific to deal with specialized requirements.
+A plugin is code that extends the Amplication developer platform by adding new features or modifying existing functionality.
+The features incorporated can be generic, useful to a wide variety of users, or can be very specific to deal with specialized requirements.
 
 If you or your organization have a specific workflow, install an existing plugin or write one to customize the platform to perform your required tasks.