add a note about using the same type name in evolved serializers

Author: mdumandag

docs/serialization.rst

@@ -264,6 +264,9 @@ and types. Hazelcast uses the write method of the serializer to extract a
 schema out of the object, hence any conditional code that may or may not run
 depending on the object in that method might result in an undefined behavior.
 
+Additionally, evolved serializers must have the same type name with the
+initial version of the serializer.
+
 Limitations
 ~~~~~~~~~~~
 

hazelcast/serialization/api.py

@@ -2646,7 +2646,7 @@ def get_type_name(self) -> str:
         :const`CompactSerializableClass`.
 
         If the class is ever evolved by adding or removing fields,
-        the type  name for the evolved serializers must be the same
+        the type name for the evolved serializers must be the same
         with the initial version.
 
         Returns: