Skip to content

Commit 678cc74

Browse files
Update modernizing-existing-add-ons.md
1 parent f14a49d commit 678cc74

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/development/modernizing-existing-add-ons.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,21 +11,21 @@
1111

1212

1313

14-
The ExpressionEngine 7.2 release brough a new add-on developemnt approach, which generates the majority of the add-ons needed files and struture. It also bring additional organization to how add-ons are developed.
14+
The ExpressionEngine 7.2 release brought a new add-on development approach, which generates the majority of the add-on's needed files and structure. It also brings additional organization to how add-ons are developed.
1515

1616
NOTE: These changes do NOT break existing add-ons. The old development methodologies will still work.
1717

18-
The idea of a plugin, module, extension, fieldtype, etc. no longer exist. Instead an add-on can have a template tag, or a field-type, or an extention.
18+
The idea of a plugin, module, extension, fieldtype, etc. no longer exists. Instead, an add-on can have a template tag, a fieldtype, or an extension.
1919

20-
In order to harness the new add-on development methodology, you will have to do a few SMALL updates to your existing add-on's.
20+
In order to harness the new add-on development methodology, you will have to do a few SMALL updates to your existing add-ons.
2121

22-
TIP: You don't have to migrate your add-on to the new development methodology. After making the following changes, you can leave your add-ons as is, and start new / additional development in the new method.
22+
TIP: You don't have to migrate your add-on to the new development methodology. After making the following changes, you can leave your add-ons as is, and start new/additional development in the new method.
2323

2424

2525
[TOC]
2626

2727
## Updating your mod.addon.php file
28-
In order to use the new approach, you will have to have your mod file use and extend the module addon service
28+
In order to use the new approach, you will have to have your mod file use and extend the module add-on service
2929

3030

3131
```
@@ -37,7 +37,7 @@ class Addon extends Module
3737

3838
## Updating your mcp.addon.php file
3939

40-
In order to use the new approach, you will have to have your mcp file use and extend the Mcp addon service
40+
In order to use the new approach, you will have to have your mcp file use and extend the Mcp add-on service
4141

4242
```
4343
use ExpressionEngine\Service\Addon\Mcp;
@@ -47,7 +47,7 @@ class Addon_mcp extends Mcp
4747

4848
## Updating your ext.addon.php file
4949

50-
In order to use the new approach, you will have to have your mcp file use and extend the Extension addon service
50+
In order to use the new approach, you will have to have your mcp file use and extend the Extension add-on service
5151

5252
```
5353
use ExpressionEngine\Service\Addon\Extension;
@@ -57,12 +57,12 @@ class Addon_ext extends Extension
5757

5858
## Updating your upd.addon.php file
5959

60-
In order to use the new approach, you will have to have your mcp file use and extend the Instaler addon service
60+
In order to use the new approach, you will have to have your mcp file use and extend the Installer add-on service
6161

6262
```
6363
use ExpressionEngine\Service\Addon\Installer;
6464
6565
class Addon_upd extends Installer
6666
```
6767
## A Note on Plugins
68-
If your add-on is currently a plugin and your looking to take advantage of the new add-on development methodologies, we recommend migrating your plugin methods (functions) to your mod file first. This can be done with a simple copy and paste.
68+
If your add-on is currently a plugin and you are looking to take advantage of the new add-on development methodologies, we recommend migrating your plugin methods (functions) to your mod file first. This can be done with a simple copy and paste.

0 commit comments

Comments
 (0)