Addresses more feedback.

Author: szabosteve

specification/inference/_types/CommonTypes.ts

@@ -782,7 +782,7 @@ export class CustomServiceSettings {
    * ```
    * If the subsequent inference requests come from a search context, the `search` key will be used and the template will be replaced with `do_search`.
    * If it comes from the ingest context `do_ingest` is used. If it's a different context that is not specified, the default value will be used. If no default is specified an empty string is used.
-   * `transition` can be:
+   * `translation` can be:
    * * `classification`
    * * `clustering`
    * * `ingest`
@@ -795,9 +795,11 @@ export class CustomServiceSettings {
    * ```
    * "query_parameters":[
    *   ["param_key", "some_value"],
-   *   ["param_key", "another_value"]
+   *   ["param_key", "another_value"],
+   *   ["other_key", "other_value"]
    * ]
    * ```
+   * If the base url is `https://www.elastic.co` it results in: `https://www.elastic.co?param_key=some_value&param_key=another_value&other_key=other_value`.
    */
   query_parameters?: UserDefinedValue
   /**
@@ -832,7 +834,7 @@ export class CustomRequestParams {
    * "request": "{\"input\":${input}}"
    * ```
    * > info
-   * > The content string needs to be a single line except using the Kibana console.
+   * > The content string needs to be a single line except when using the Kibana console.
    */
   content: string
 }

specification/inference/put_custom/PutCustomRequest.ts

@@ -32,7 +32,7 @@ import { InferenceChunkingSettings } from '@inference/_types/Services'
  *
  * The custom service gives more control over how to interact with external inference services that aren't explicitly supported through dedicated integrations.
  * The custom service gives you the ability to define the headers, url, query parameters, request body, and secrets.
- * The custom service supports the template replacement functionality, which enables you to define a template that can be replaced with the contents of a value that defines that key.
+ * The custom service supports the template replacement functionality, which enables you to define a template that can be replaced with the value associated with that key.
  * Templates are portions of a string that start with `${` and end with `}`.
  * The parameters `secret_parameters` and `task_settings` are checked for keys for template replacement. Template replacement is supported in the `request`, `headers`, `url`, and `query_parameters`.
  * If the definition (key) is not found for a template, an error message is returned.