fix(specs): normalize spelling of summaries (#5340) (generated) [skip ci]

Co-authored-by: Kai Welke <[email protected]>

Author: algolia-bot

clients/algoliasearch-client-csharp/algoliasearch/Clients/IngestionClient.cs

@@ -1739,7 +1739,7 @@ WatchResponse Push(
   );
 
   /// <summary>
-  /// Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the [pre-indexing data transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/), this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.
+  /// Pushes records through the pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints or the debugger dashboard to see the status of your task. If you want to transform your data before indexing, this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.
   /// </summary>
   ///
   /// Required API Key ACLs:
@@ -1764,7 +1764,7 @@ Task<WatchResponse> PushTaskAsync(
   );
 
   /// <summary>
-  /// Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the [pre-indexing data transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/), this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.  (Synchronous version)
+  /// Pushes records through the pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints or the debugger dashboard to see the status of your task. If you want to transform your data before indexing, this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.  (Synchronous version)
   /// </summary>
   ///
   /// Required API Key ACLs:

clients/algoliasearch-client-go/algolia/ingestion/api_ingestion.go

@@ -3333,14 +3333,12 @@ public CompletableFuture<WatchResponse> pushAsync(@Nonnull String indexName, @No
   }
 
   /**
-   * Pushes records through the Pipeline, directly to an index. You can make the call synchronous by
+   * Pushes records through the pipeline, directly to an index. You can make the call synchronous by
    * providing the `watch` parameter, for asynchronous calls, you can use the observability
-   * endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the
-   * [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * endpoints or the debugger dashboard to see the status of your task. If you want to transform
+   * your data before indexing, this is the recommended way of ingesting your records. This method
+   * is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when
+   * many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3360,14 +3358,12 @@ public WatchResponse pushTask(
   }
 
   /**
-   * Pushes records through the Pipeline, directly to an index. You can make the call synchronous by
+   * Pushes records through the pipeline, directly to an index. You can make the call synchronous by
    * providing the `watch` parameter, for asynchronous calls, you can use the observability
-   * endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the
-   * [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * endpoints or the debugger dashboard to see the status of your task. If you want to transform
+   * your data before indexing, this is the recommended way of ingesting your records. This method
+   * is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when
+   * many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3381,14 +3377,12 @@ public WatchResponse pushTask(@Nonnull String taskID, @Nonnull PushTaskPayload p
   }
 
   /**
-   * Pushes records through the Pipeline, directly to an index. You can make the call synchronous by
+   * Pushes records through the pipeline, directly to an index. You can make the call synchronous by
    * providing the `watch` parameter, for asynchronous calls, you can use the observability
-   * endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the
-   * [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * endpoints or the debugger dashboard to see the status of your task. If you want to transform
+   * your data before indexing, this is the recommended way of ingesting your records. This method
+   * is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when
+   * many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3402,14 +3396,12 @@ public WatchResponse pushTask(@Nonnull String taskID, @Nonnull PushTaskPayload p
   }
 
   /**
-   * Pushes records through the Pipeline, directly to an index. You can make the call synchronous by
+   * Pushes records through the pipeline, directly to an index. You can make the call synchronous by
    * providing the `watch` parameter, for asynchronous calls, you can use the observability
-   * endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the
-   * [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * endpoints or the debugger dashboard to see the status of your task. If you want to transform
+   * your data before indexing, this is the recommended way of ingesting your records. This method
+   * is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when
+   * many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3420,14 +3412,12 @@ public WatchResponse pushTask(@Nonnull String taskID, @Nonnull PushTaskPayload p
   }
 
   /**
-   * (asynchronously) Pushes records through the Pipeline, directly to an index. You can make the
+   * (asynchronously) Pushes records through the pipeline, directly to an index. You can make the
    * call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the
-   * observability endpoints and/or debugger dashboard to see the status of your task. If you want
-   * to leverage the [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * observability endpoints or the debugger dashboard to see the status of your task. If you want
+   * to transform your data before indexing, this is the recommended way of ingesting your records.
+   * This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is
+   * useful when many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3465,14 +3455,12 @@ public CompletableFuture<WatchResponse> pushTaskAsync(
   }
 
   /**
-   * (asynchronously) Pushes records through the Pipeline, directly to an index. You can make the
+   * (asynchronously) Pushes records through the pipeline, directly to an index. You can make the
    * call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the
-   * observability endpoints and/or debugger dashboard to see the status of your task. If you want
-   * to leverage the [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * observability endpoints or the debugger dashboard to see the status of your task. If you want
+   * to transform your data before indexing, this is the recommended way of ingesting your records.
+   * This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is
+   * useful when many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3486,14 +3474,12 @@ public CompletableFuture<WatchResponse> pushTaskAsync(@Nonnull String taskID, @N
   }
 
   /**
-   * (asynchronously) Pushes records through the Pipeline, directly to an index. You can make the
+   * (asynchronously) Pushes records through the pipeline, directly to an index. You can make the
    * call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the
-   * observability endpoints and/or debugger dashboard to see the status of your task. If you want
-   * to leverage the [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * observability endpoints or the debugger dashboard to see the status of your task. If you want
+   * to transform your data before indexing, this is the recommended way of ingesting your records.
+   * This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is
+   * useful when many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)
@@ -3510,14 +3496,12 @@ public CompletableFuture<WatchResponse> pushTaskAsync(
   }
 
   /**
-   * (asynchronously) Pushes records through the Pipeline, directly to an index. You can make the
+   * (asynchronously) Pushes records through the pipeline, directly to an index. You can make the
    * call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the
-   * observability endpoints and/or debugger dashboard to see the status of your task. If you want
-   * to leverage the [pre-indexing data
-   * transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/),
-   * this is the recommended way of ingesting your records. This method is similar to `push`, but
-   * requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target
-   * the same `indexName`.
+   * observability endpoints or the debugger dashboard to see the status of your task. If you want
+   * to transform your data before indexing, this is the recommended way of ingesting your records.
+   * This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is
+   * useful when many `destinations` target the same `indexName`.
    *
    * @param taskID Unique identifier of a task. (required)
    * @param pushTaskPayload (required)

clients/algoliasearch-client-java/algoliasearch/src/main/java/com/algolia/api/IngestionClient.java

@@ -317,7 +317,6 @@ export function createCompositionClient({
      *
      * Required API Key ACLs:
      *  - editSettings
-     *  - settings
      * @param deleteComposition - The deleteComposition object.
      * @param deleteComposition.compositionID - Unique Composition ObjectID.
      * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions.
@@ -352,7 +351,6 @@ export function createCompositionClient({
      *
      * Required API Key ACLs:
      *  - editSettings
-     *  - settings
      * @param deleteCompositionRule - The deleteCompositionRule object.
      * @param deleteCompositionRule.compositionID - Unique Composition ObjectID.
      * @param deleteCompositionRule.objectID - Unique identifier of a rule object.
@@ -422,6 +420,7 @@ export function createCompositionClient({
      * Retrieves a rule by its ID. To find the object ID of rules, use the [`search` operation](#tag/Rules/operation/searchRules).
      *
      * Required API Key ACLs:
+     *  - editSettings
      *  - settings
      * @param getRule - The getRule object.
      * @param getRule.compositionID - Unique Composition ObjectID.
@@ -566,7 +565,6 @@ export function createCompositionClient({
      *
      * Required API Key ACLs:
      *  - editSettings
-     *  - settings
      * @param putComposition - The putComposition object.
      * @param putComposition.compositionID - Unique Composition ObjectID.
      * @param putComposition.composition - The composition object.
@@ -617,7 +615,6 @@ export function createCompositionClient({
      *
      * Required API Key ACLs:
      *  - editSettings
-     *  - settings
      * @param putCompositionRule - The putCompositionRule object.
      * @param putCompositionRule.compositionID - Unique Composition ObjectID.
      * @param putCompositionRule.objectID - Unique identifier of a rule object.

clients/algoliasearch-client-javascript/packages/client-composition/src/compositionClient.ts

@@ -1854,7 +1854,7 @@ export function createIngestionClient({
     },
 
     /**
-     * Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to see the status of your task. If you want to leverage the [pre-indexing data transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/), this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.
+     * Pushes records through the pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints or the debugger dashboard to see the status of your task. If you want to transform your data before indexing, this is the recommended way of ingesting your records. This method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.
      *
      * Required API Key ACLs:
      *  - addObject