Spelling in comments.

Author: oskarb

src/NHibernate.Test/Immutable/EntityWithMutableCollection/AbstractEntityWithManyToManyTest.cs

@@ -484,7 +484,7 @@ public void CreateWithNonEmptyManyToManyCollectionMergeWithNewElement()
 			s.Close();
 
 			AssertInsertCount(1);
-			AssertUpdateCount(isContractVersioned && isPlanVersioned ? 1 : 0);  // NH-specific: Hibernate issues a seperate UPDATE for the version number
+			AssertUpdateCount(isContractVersioned && isPlanVersioned ? 1 : 0);  // NH-specific: Hibernate issues a separate UPDATE for the version number
 			ClearCounts();
 
 			s = OpenSession();

src/NHibernate.Test/ReadOnly/ReadOnlyVersionedNodes.cs

@@ -617,7 +617,7 @@ public void MergeDetachedChildWithNewParentCommitWithReadOnlyChild()
 			s.Transaction.Commit();
 			s.Close();
 
-			AssertUpdateCount(0); // NH-specific: Hibernate issues a seperate UPDATE for the version number
+			AssertUpdateCount(0); // NH-specific: Hibernate issues a separate UPDATE for the version number
 			AssertInsertCount(1);
 			ClearCounts();
 
@@ -667,7 +667,7 @@ public void GetChildMakeReadOnlyThenMergeDetachedChildWithNewParent()
 			s.Transaction.Commit();
 			s.Close();
 
-			AssertUpdateCount(0); // NH-specific: Hibernate issues a seperate UPDATE for the version number
+			AssertUpdateCount(0); // NH-specific: Hibernate issues a separate UPDATE for the version number
 			AssertInsertCount(1);
 			ClearCounts();
 

src/NHibernate/Dialect/InformixDialect.cs

@@ -258,7 +258,7 @@ public override bool SupportsIdentityColumns
 
 		/// <summary>
 		/// Whether this dialect have an Identity clause added to the data type or a
-		/// completely seperate identity data type
+		/// completely separate identity data type
 		/// </summary>
 		public override bool HasDataTypeInIdentityColumn
 		{

src/NHibernate/Engine/Transaction/Isolater.cs

@@ -18,7 +18,7 @@ namespace NHibernate.Engine.Transaction
   ///  </listheader>
   ///  <item>
 	///      <term><see cref="DoIsolatedWork"/> </term>
-	///      <description>makes sure the work to be done is performed in a seperate, distinct transaction</description>
+	///      <description>makes sure the work to be done is performed in a separate, distinct transaction</description>
   ///  </item>
 	///  <item>
 	///      <term><see cref="DoNonTransactedWork"/> </term>
@@ -32,7 +32,7 @@ public class Isolater
 
 		/// <summary> 
 		/// Ensures that all processing actually performed by the given work will
-		/// occur on a seperate transaction. 
+		/// occur on a separate transaction. 
 		/// </summary>
 		/// <param name="work">The work to be performed. </param>
 		/// <param name="session">The session from which this request is originating. </param>

src/NHibernate/Event/Default/DefaultMergeEventListener.cs

@@ -418,7 +418,7 @@ private static bool IsVersionChanged(object entity, IEventSource source, IEntity
 			//
 			// This second condition is a special case which allows
 			// an entity to be merged during the same transaction
-			// (though during a seperate operation) in which it was
+			// (though during a separate operation) in which it was
 			// originally persisted/saved
 			bool changed =
 				!persister.VersionType.IsSame(persister.GetVersion(target, source.EntityMode),

src/NHibernate/Hql/Ast/ANTLR/SqlGenerator.cs

@@ -27,7 +27,7 @@ public partial class SqlGenerator : IErrorReporter
 		 * all append invocations on the buf should go through this Output instance variable.
 		 * The value of this variable may be temporarily substitued by sql function processing code
 		 * to catch generated arguments.
-		 * This is because sql function templates need arguments as seperate string chunks
+		 * This is because sql function templates need arguments as separate string chunks
 		 * that will be assembled into the target dialect-specific function call.
 		 */
 		private readonly List<ISqlWriter> outputStack = new List<ISqlWriter>();

src/NHibernate/ICriteria.cs

@@ -121,7 +121,7 @@ public interface ICriteria : ICloneable
 		/// Specify an association fetching strategy.  Currently, only
 		/// one-to-many and one-to-one associations are supported.
 		/// </summary>
-		/// <param name="associationPath">A dot seperated property path.</param>
+		/// <param name="associationPath">A dot separated property path.</param>
 		/// <param name="mode">The Fetch mode.</param>
 		/// <returns></returns>
 		ICriteria SetFetchMode(string associationPath, FetchMode mode);
@@ -181,7 +181,7 @@ public interface ICriteria : ICloneable
 		/// Create a new <see cref="ICriteria" />, "rooted" at the associated entity,
 		/// using the specified join type.
 		/// </summary>
-		/// <param name="associationPath">A dot-seperated property path</param>
+		/// <param name="associationPath">A dot-separated property path</param>
 		/// <param name="joinType">The type of join to use</param>
 		/// <returns>The created "sub criteria"</returns>
 		ICriteria CreateCriteria(string associationPath, JoinType joinType);

src/NHibernate/IMultiQuery.cs

@@ -135,7 +135,7 @@ public interface IMultiQuery
 
 		/// Should the query force a refresh of the specified query cache region?
 		/// This is particularly useful in cases where underlying data may have been
-		/// updated via a seperate process (i.e., not modified through Hibernate) and
+		/// updated via a separate process (i.e., not modified through Hibernate) and
 		/// allows the application to selectively refresh the query cache regions
 		/// based on its knowledge of those events.
 		/// <param name="forceCacheRefresh">Should the query result in a forcible refresh of

src/NHibernate/Id/TableGenerator.cs

@@ -25,7 +25,7 @@ namespace NHibernate.Id
 	/// <c>System.Int32</c>
 	/// </p>
 	/// <p>
-	/// The hi value MUST be fetched in a seperate transaction to the <c>ISession</c>
+	/// The hi value MUST be fetched in a separate transaction to the <c>ISession</c>
 	/// transaction so the generator must be able to obtain a new connection and commit it.
 	/// Hence this implementation may not be used when the user is supplying connections.
 	/// </p>

src/NHibernate/Id/TableHiLoGenerator.cs

@@ -30,7 +30,7 @@ namespace NHibernate.Id
 	/// <c>schema</c> are optional.
 	/// </p>
 	/// <p>
-	/// The hi value MUST be fecthed in a seperate transaction to the <c>ISession</c>
+	/// The hi value MUST be fecthed in a separate transaction to the <c>ISession</c>
 	/// transaction so the generator must be able to obtain a new connection and 
 	/// commit it. Hence this implementation may not be used when the user is supplying
 	/// connections.  In that case a <see cref="SequenceHiLoGenerator"/> would be a 

src/NHibernate/Linq/Visitors/QuerySourceIdentifier.cs

@@ -8,7 +8,7 @@ namespace NHibernate.Linq.Visitors
 	/// Identifies and names - using <see cref="QuerySourceNamer"/> - all QueryModel query sources
 	/// </summary>
 	/// <remarks>
-	/// It may seem expensive to do this as a seperate visitation of the query model, but unfortunately
+	/// It may seem expensive to do this as a separate visitation of the query model, but unfortunately
 	/// trying to identify query sources on the fly (i.e. while parsing the query model to generate
 	/// the HQL expression tree) means a query source may be referenced by a <c>QuerySourceReference</c>
 	/// before it has been identified - and named.

src/NHibernate/Mapping/Property.cs

@@ -263,7 +263,7 @@ public bool IsLazy
 			{
 				// NH Specific: Hibernate doesn't make a distinction between
 				// lazy and no-proxy, but NHibernate does. While Hibernate tracks
-				// just whatever a property is lazy, we need to track lazy/no-proxy seperatedly.
+				// just whatever a property is lazy, we need to track lazy/no-proxy separately.
 
 				return isLazy;
 			}

src/NHibernate/Proxy/ILazyInitializer.cs

@@ -84,7 +84,7 @@ public interface ILazyInitializer
 		/// Associate the proxy with the given session.
 		///
 		/// Care should be given to make certain that the proxy is added to the session's persistence context as well
-		/// to maintain the symmetry of the association.  That must be done seperately as this method simply sets an
+		/// to maintain the symmetry of the association.  That must be done separately as this method simply sets an
 		/// internal reference.  We do also check that if there is already an associated session that the proxy
 		/// reference was removed from that previous session's persistence context.
 		/// </summary>