fix typos

dspace-api/src/main/java/org/dspace/browse/SolrBrowseCreateDAO.java

@@ -107,7 +107,7 @@ public void additionalIndex(Context context, DSpaceObject dso, SolrInputDocument
         Item item = (Item) dso;
 
         // faceting for metadata browsing. It is different than search facet
-        // because if there are authority with variants support we wan't all the
+        // because if there are authority with variants support we want all the
         // variants to go in the facet... they are sorted by count so just the
         // prefered label is relevant
         for (BrowseIndex bi : bis)

dspace-api/src/main/java/org/dspace/curate/Curator.java

@@ -40,7 +40,7 @@ public class Curator
     public static final int CURATE_NOTASK = -3;
     /** no assigned status code - typically because task not yet performed */
     public static final int CURATE_UNSET = -2;
-    /** task encountered a error in processing */
+    /** task encountered an error in processing */
     public static final int CURATE_ERROR = -1;
     /** task completed successfully */
     public static final int CURATE_SUCCESS = 0;

dspace-xmlui/src/main/webapp/themes/mobile/mobile.xsl

@@ -790,7 +790,7 @@
 </xsl:template>
 
 <!-- ds-options -->
-<!-- the browse section is being implemented in the front page custoization -->
+<!-- the browse section is being implemented in the front page customization -->
 <xsl:template match="dri:options">&#160;
 </xsl:template>
 

dspace/config/crosswalks/oai/xoai.xml

@@ -48,7 +48,7 @@
             <Transformer ref="driverTransformer"/>
             <!-- The driver filter -->
             <Filter ref="driverFilter"/>
-            <!-- Just an alias, if fact it returns all items within the driver context -->
+            <!-- Just an alias, in fact it returns all items within the driver context -->
             <Set ref="driverSet"/>
             <!-- Metadata Formats -->
             <Format ref="oaidc"/>
@@ -73,7 +73,7 @@
             <Transformer ref="openaireTransformer"/>
             <!-- OpenAIRE filter -->
             <Filter ref="openAireFilter"/>
-            <!-- Just an alias, if fact it returns all items within the driver context -->
+            <!-- Just an alias, in fact it returns all items within the driver context -->
             <Set ref="openaireSet"/>
             <!-- Metadata Formats -->
             <Format ref="oaidc"/>

dspace/config/modules/authentication-ldap.cfg

@@ -152,8 +152,8 @@ autoregister = true
 # specified by the right part of the groupmap value (after the ":").
 # One user may belong to multiple groups.
 #login.groupmap.1 = ou=ldap-dept1:dspace-group1
-#login.groupmap.2 = ou=ldap-dept2:dspave-groupA
-#login.groupmap.3 = ou=ldap-dept3:dspave-groupA
+#login.groupmap.2 = ou=ldap-dept2:dspace-groupA
+#login.groupmap.3 = ou=ldap-dept3:dspace-groupA
 
 # If this property is uncommented, it changes the meaning of the left part of
 # the groupmap value (before the ":") as follows.
@@ -164,6 +164,6 @@ autoregister = true
 # the ":").
 #login.groupmap.attribute = group
 #login.groupmap.1 = ldap-dept1:dspace-group1
-#login.groupmap.2 = ldap-dept2:dspave-groupA
-#login.groupmap.3 = ldap-dept3:dspave-groupA
+#login.groupmap.2 = ldap-dept2:dspace-groupA
+#login.groupmap.3 = ldap-dept3:dspace-groupA
 

dspace/config/spring/api/bte.xml

@@ -107,7 +107,7 @@
 	    <property name="dataloadersMap">
 	        <map>
 	            <!-- Specify here any data loaders you want to include in the submission lookup process.
-	            	Dataloades must either extend the "NetworkSubmissionLookupDataLoader" abstract class
+	            	Dataloaders must either extend the "NetworkSubmissionLookupDataLoader" abstract class
 	            	or conform to "FileDataLoader" interface of BTE -->
 	            <entry key="pubmed" value-ref="pubmedOnlineDataLoader"/>
 	            <entry key="crossref" value-ref="crossRefOnlineDataLoader"/>
@@ -146,7 +146,7 @@
 	    <property name="configurationService" ref="org.dspace.services.ConfigurationService"/>
 	    <property name="fieldKeys">
 	        <list>
-	            <!-- Specify the internal BTE keys that this modifiers needs to be applied -->
+	            <!-- Specify the internal BTE keys that this modifier needs to be applied for -->
 	        	<value>arxivCategory</value>
 	        </list>
 	    </property>
@@ -160,7 +160,7 @@
 	    <property name="defaultValue" value="Subjected to Journal"/>
 	    <property name="fieldKeys">
 	        <list>
-	            <!-- Specify the internal BTE keys that this modifiers needs to be applied -->
+	            <!-- Specify the internal BTE keys that this modifier needs to be applied for -->
 	        	<value>publicationStatus</value>
 	        </list>
 	    </property>
@@ -268,11 +268,11 @@
 	<!-- Each entry in a CSV is a row, and each column represents the same data 
 		in each entry. For example the first column might record the item title, 
 		the second the authors etc. The key of the field map is this number. Note 
-		that the first column is number 0. The CSV data loader has these extra parameters 
+		that the first column is number 0. The CSV data loader has the following extra parameters 
 		that configure its behaviour: - skipLines: a number that instructs the reader 
 		to ignore the first lines in the input file. Default value: 0 - separator: 
 		a character that signifies how the values are separated. Default value ',' 
-		-quoteChar: individual valued could include the separator character. For 
+		-quoteChar: individual values could include the separator character. For 
 		example if the separator is ',' and there is an abstract, there is a high 
 		probability that it will contain commas. If the value is quoted using the 
 		quoteChar then separator characters inside it will be ignored. Default value 
@@ -316,7 +316,7 @@
 		<property name="skipLines" value="1" />
 	</bean>
 
-	<!-- The map for the RIS data loader has to have as keys the RIS tags that 
+	<!-- The keys in the RIS data loader map have to be the RIS tags that 
 		need to be loaded. -->
 	<bean id="risDataLoader" class="gr.ekt.bteio.loaders.RISDataLoader">
 		<property name="fieldMap">
@@ -526,7 +526,7 @@
 	<!-- **************************************************************************************************** -->
 
 	<!-- The output generator needs a configuration on how to map internal records 
-		to the DSpace metadata fields. The following map specifies this relationship. 
+		to DSpace metadata fields. The following map specifies this relationship. 
 		The value needs to be the label that the record internally associates with 
 		the specific data and it is specified in the data loader beans. The key is 
 		in the format of <schema>.<element>[.<qualifier>] and specified the dspace 

dspace/config/spring/api/identifier-service.xml

@@ -30,11 +30,11 @@
     <!-- provider to mint and register DOIs with DSpace.
          To mint DOIs you need a registration agency. The DOIIdentifierProvider
          maintains the doi database table and handling of DSpaceObject. It uses
-         a DOIConnector that handle all API calls to your DOI registration
-         agency. Please configure a DOIConnector as well!-->
+         a DOIConnector that handles all API calls to your DOI registration
+         agency. Please configure a DOIConnector as well! -->
 
-    <!-- To mint DOIs with DSpace get an agreement with a DOI registration
-         agency,  take a look into dspace.cfg, and remove this comment
+    <!-- In order to mint DOIs with DSpace, get an agreement with a DOI registration
+         agency,  take a look into dspace.cfg, and uncomment this.
     <bean id="org.dspace.identifier.DOIIdentifierProvider"
         class="org.dspace.identifier.DOIIdentifierProvider"
         scope="singleton">
@@ -47,13 +47,13 @@
 
     <!-- The DOIConnector will handle the API calls to your DOI registration
          agency for the DOIIdentifierProvider. If your registration agency
-         tells you to use DataCites API directly you can use the
+         tells you to use the DataCite API directly, you can use the
          DataCiteConnector. If your registration agency is not part of DataCite
-         or provides their own API you have to implement a DOIConnector.
-         EZID f.e. is part of DataCite but provides their own APIs. The following
+         or provides their own API, you have to implement a DOIConnector.
+         e.g. EZID is part of DataCite but provides their own APIs. The following
          DataCiteConnector won't work if EZID is your registration agency.
     -->
-    <!-- Remove this comment to use DataCite API directly as DOIConnector.
+    <!-- Uncomment this to use the DataCite API directly as DOIConnector.
     <bean id="org.dspace.identifier.doi.DOIConnector"
         class="org.dspace.identifier.doi.DataCiteConnector"
         scope="singleton">

dspace/config/spring/api/sherpa.xml

@@ -30,7 +30,7 @@
 						</list>
 					</property>
 				</bean>
-				<!-- Use the follow if you have the SHERPARoMEOJournalTitle enabled
+				<!-- Uncomment this bean if you have SHERPARoMEOJournalTitle enabled
 				<bean class="org.dspace.app.sherpa.submit.MetadataAuthorityISSNExtractor">
 					<property name="metadataList">
 						<list>