diff --git a/hazelcast/src/main/java/com/hazelcast/core/IdGenerator.java b/hazelcast/src/main/java/com/hazelcast/core/IdGenerator.java
index <HASH>..<HASH> 100644
--- a/hazelcast/src/main/java/com/hazelcast/core/IdGenerator.java
+++ b/hazelcast/src/main/java/com/hazelcast/core/IdGenerator.java
@@ -25,7 +25,7 @@ package com.hazelcast.core;
  * doing remote call for every call to {@link #newId()}, it does it less frequently. It checks out a chunk, e.g. 1..1000 and
  * as long as it has not yet consumed all the ids in its chunk, then no remote call is done.
  *
- * It can be that id's generated by different cluster members will get out of order because each member will get its own chunk. It
+ * It can be that ids generated by different cluster members will get out of order because each member will get its own chunk. It
  * can be that member 1 has chunk 1..1000 and member 2 has 1001..2000. Therefore, member 2 will automatically have ids that
  * are out of order with the ids generated by member 1.
  */
copyedit. ids, not id's, no ' with plurals.