fix comments.

Author: Rachelint

datafusion/physical-plan/src/aggregates/group_values/column.rs

@@ -207,9 +207,8 @@ impl<const STREAMING: bool> GroupValuesColumn<STREAMING> {
 
     /// Scalarized intern
     ///
-    /// This is used only for `streaming aggregation`,
-    /// because it depends on the order between `input rows` and their corresponding
-    /// `group indices`.
+    /// This is used only for `streaming aggregation`, because `streaming aggregation`
+    /// depends on the order between `input rows` and their corresponding `group indices`.
     ///
     /// For example, assuming `input rows` in `cols` with 4 new rows
     /// (not equal to `exist rows` in `group_values`, and need to create
@@ -222,7 +221,7 @@ impl<const STREAMING: bool> GroupValuesColumn<STREAMING> {
     ///   row4
     /// ```
     ///
-    /// # In [`GroupValuesColumn`], their `group indices` will be
+    /// # In `scalarized_intern`, their `group indices` will be
     ///
     /// ```text
     ///   row1 --> 0
@@ -234,7 +233,7 @@ impl<const STREAMING: bool> GroupValuesColumn<STREAMING> {
     /// `Group indices` order agrees with their input order, and the `streaming aggregation`
     /// depends on this.
     ///
-    /// # However In [`VectorizedGroupValuesColumn`], their `group indices` will be
+    /// # However In `vectorized_intern`, their `group indices` will be
     ///
     /// ```text
     ///   row1 --> 2
@@ -1020,7 +1019,7 @@ impl<const STREAMING: bool> GroupValues for GroupValuesColumn<STREAMING> {
         self.hashes_buffer.clear();
         self.hashes_buffer.shrink_to(count);
 
-        // Such structure is only used in `non-streaming` case
+        // Such structures are only used in `non-streaming` case
         if !STREAMING {
             self.group_index_lists.clear();
             self.emit_group_index_list_buffer.clear();