diff --git a/documentation/18.01/solutions/iron-eiffel-package-repository.wiki b/documentation/18.01/solutions/iron-eiffel-package-repository.wiki
index c6ad4860..c704d47e 100644
--- a/documentation/18.01/solutions/iron-eiffel-package-repository.wiki
+++ b/documentation/18.01/solutions/iron-eiffel-package-repository.wiki
@@ -16,7 +16,7 @@ Most often a package is a library or a set of libraries, but it could also other
 
 Certainly the IRON repository is a repository of Eiffel libraries. However, sometimes libraries are used together, or cross reference one another, and thus are appropriate to be delivered together as a unit. 
 Such unit can also include other types of files, such as external .c files that may need to be compiled on the local platform to make .LIB or .OBJ files available to the linker (.a or .o on Unix and Linux systems), scripts or executable that need to be run as part of the installation process (e.g. to generate other files required by the library, install environment variables, generate source code from LEX files), or tool kits that are part of, or needed by, the library.  
-Since the IRON repository permits programmers to install software components in "units", and since sometimes those units can contain more than one library, as well as other types of files, a new term was required to convey this concept:  package.
+Since the IRON repository permits programmers to install software components in "units", and since sometimes those units can contain more than one library, as well as other types of files, a new term was required to convey this concept:  package.
 
 {{Definition|package|a downloadable unit of software from an IRON repository that contains one or more Eiffel libraries and their related files.}}
 
@@ -269,7 +269,7 @@ The "iron" executable is used to perform various operations such as search, inst
 </code>
 (or <nowiki>iron install https://iron.eiffel.com/14.05/com.eiffel/library/base</nowiki>)
 
-:(This latter form is useful in resolving name conflicts when, for instance, you have multiple IRON repositories registered on your system, and two or more contain a packaged called "base".)
+:(This latter form is useful in resolving name conflicts when, for instance, you have multiple IRON repositories registered on your system, and two or more contain a packaged called "base".)
 
 ===Uninstall a package===
 <code> iron remove  base
@@ -298,7 +298,7 @@ iron  repository  --remove https://custom.example.com/14.05
 
 ===Multiple-Repository Name Conflict Resolution===
 
-If you have more than one IRON repository registered on your system, it is possible that the same package name may exist on more than one repository.  If this is the case, and you attempt to perform operations using that name only, the repository that will be used will be the first repository in the list that contains a package with that name.  If you need the package with that name from a different repository, then use the "id" or "uri" form of the identifying the package you want.
+If you have more than one IRON repository registered on your system, it is possible that the same package name may exist on more than one repository.  If this is the case, and you attempt to perform operations using that name only, the repository that will be used will be the first repository in the list that contains a package with that name.  If you need the package with that name from a different repository, then use the "id" "uri" form of the identifying the package you want.
 
 If the sequence of repositories is not to your liking, you can change it in three ways:
 
@@ -457,3 +457,4 @@ More features are planned or are already under development:
 :* ability to upgrade of packages already installed
 :* extended post-installation operations
 :* more features that users may request or suggest.
+