Fix comment typos: succesfully→successfully, sould→should, dont→don't (#18291)

Author: Jah-yee

pinot-core/src/main/java/org/apache/pinot/core/data/manager/realtime/RealtimeSegmentDataManager.java

@@ -1016,7 +1016,7 @@ public void run() {
                 TimeUnit.MILLISECONDS.toSeconds(now() - initialConsumptionEnd));
       }
       // There is a race condition that the destroy() method can be called which ends up calling stop on the consumer.
-      // The destroy() method does not wait for the thread to terminate (and reasonably so, we dont want to wait
+      // The destroy() method does not wait for the thread to terminate (and reasonably so, we don't want to wait
       // forever).
       // Since the _shouldStop variable is set to true only in stop() method, we know that the metric will be destroyed,
       // so it is ok not to mark it non-consuming, as the main thread will clean up this metric in destroy() method

pinot-integration-tests/src/test/java/org/apache/pinot/integration/tests/PurgeMinionClusterIntegrationTest.java

@@ -203,7 +203,7 @@ protected TableTaskConfig getPurgeTaskConfig() {
   public void testFirstRunPurge()
       throws Exception {
     // Expected purge task generation :
-    // 1. No previous purge run so all segment should be processed and purge metadata sould be added to the segments
+    // 1. No previous purge run so all segment should be processed and purge metadata should be added to the segments
     // 2. Check that we cannot run on same time two purge generation ensuring running segment will be skipped
     // 3. Check segment ZK metadata to ensure purge time is updated into the metadata
     // 4. Check after the first run of the purge if we rerun a purge task generation no task should be scheduled

pinot-query-planner/src/main/java/org/apache/pinot/calcite/rel/rules/PinotRuleUtils.java

@@ -100,7 +100,7 @@ public static boolean isAggregate(RelNode rel) {
    * <ul>
    *   <li>`RelNode` that are single-in, single-out are possible (Project/Filter/)</li>
    *   <li>`Join` can be stacked on top if we only consider SEMI-JOIN</li>
-   *   <li>`Window` should be allowed but we dont have impl for Window on leaf, so not yet included.</li>
+   *   <li>`Window` should be allowed but we don't have impl for Window on leaf, so not yet included.</li>
    *   <li>`Sort` should be allowed but we need to reorder Sort and Join first, so not yet included.</li>
    * </ul>
    */

pinot-segment-local/src/main/java/org/apache/pinot/segment/local/utils/tablestate/TableStateUtils.java

@@ -76,12 +76,12 @@ public static List<String> getSegmentsInGivenStateForThisInstance(HelixManager h
   }
 
   /**
-   * Checks if all segments for the given @param tableNameWithType were succesfully loaded
+   * Checks if all segments for the given @param tableNameWithType were successfully loaded
    * This function will get all segments in IDEALSTATE and CURRENTSTATE for the given table,
    * and then check if all ONLINE segments in IDEALSTATE match with CURRENTSTATE.
    * @param helixManager helix manager for the server instance
    * @param tableNameWithType table name for which segment state is to be checked
-   * @return true if all segments for the given table are succesfully loaded. False otherwise
+   * @return true if all segments for the given table are successfully loaded. False otherwise
    */
   public static boolean isAllSegmentsLoaded(HelixManager helixManager, String tableNameWithType) {
     List<String> onlineSegments =