1.1 --- a/api.mdr/arch/arch-mdr.xml	Thu Apr 08 14:23:33 2004 +0000
     1.2 +++ b/api.mdr/arch/arch-mdr.xml	Fri Apr 09 08:43:11 2004 +0000
     1.3 @@ -675,7 +675,7 @@
     1.4  <answer id="lookup-lookup">
     1.5  The lookup is used to find implementation of MDRManager, XMIReader, XMIWriter, JMIMapper and
     1.6      some other less significant interfaces from the api package. The order is important in case
     1.7 -    of JMIMapper and XMIReader instnaces, since we have several implementations of those
     1.8 +    of JMIMapper and XMIReader instances, since we have several implementations of those
     1.9      (e.g. a JMIMapper that generates java sources and a JMIMapper that generates class files directly).
    1.10      User is able to choose which one to invoke by changing order of them in the lookup.
    1.11  </answer>
    1.12 @@ -961,8 +961,8 @@
    1.13      <ul>
    1.14          <li>Add setProperties(Map) method to the MDRepository interface - its contract will be
    1.15   that it has to be called once and only once and it has to be called as the first method
    1.16 - on a given instnace - this method will initialize the repository instnace.</li>
    1.17 -        <li>Repositories will be registered in layer as *.instnace files. All the properties
    1.18 + on a given instance - this method will initialize the repository instance.</li>
    1.19 +        <li>Repositories will be registered in layer as *.instance files. All the properties
    1.20   of a given repository (passed to it in setProperties method as name-value pairs) will be
    1.21   declared as file attributes. An open issue is that it is expected that most modules will
    1.22   want to use (register a new instance of) the default implementation of MDRepository provided by MDR module - NBMDRepositoryImpl class.