--- deliantra/server/pod/extensions.pod	2006/09/08 15:34:56	1.1
+++ deliantra/server/pod/extensions.pod	2006/09/09 23:22:06	1.2
@@ -12,9 +12,9 @@
 
 You can "attach" extensions to global events, to type/subtypes,
 to specifix objects, to players and to maps.
- On top of that a extension can implement new user commands.
+On top of that an extension can implement new user commands.
 
-If a extension for example wants to attach itself to all jeweler
+If an extension for example wants to attach itself to all jeweler
 skills it has to attach itself like this:
 
    cf::attach_to_type cf::SKILL, cf::SK_JEWELER,
@@ -39,7 +39,7 @@
 
 The map attachments work like this:
 
-If a extension wants to attach itself to the 'trigger' event (this is
+If an extension wants to attach itself to the 'trigger' event (this is
 the event that is generated when a connection is activated (pushed or
 released)), it has to do this:
 
@@ -116,7 +116,7 @@
 
 =head2 Defining new user commands
 
-If a extension wants to redefine a user command it does it like this:
+If an extension wants to redefine a user command it does it like this:
 
    cf::register_command invite => 10, sub {
       my ($who, $args) = @_;