Update from SAP DITA CMS (squashed):

commit 32a957dc110b7b46719f38d5e82043fc24a98671
Author: REDACTED
Date:   Mon May 5 11:24:46 2025 +0000

    Update from SAP DITA CMS 2025-05-05 11:24:46

    Project: dita-all/bex1621329160251
    Project map: d3e749bbac3d4f728c12228db6629c45.ditamap
    Output: loiodaa66b2ef49f48539fa2882d82d5b619
    Language: en-US
    Builddable map: f17fa8568d0448c685f2a0301061a6ee.ditamap

commit 949a3ea237bcab55ed1682148a26d68b45d6f24d
Author: REDACTED
Date:   Mon May 5 11:10:48 2025 +0000

    Update from SAP DITA CMS 2025-05-05 11:10:48

    Project: dita-all/ayn1620809929290
    Project map: 8a3894192639433b9ba1f87efe78bfd1.ditamap
    Output: loio62559d01add8414eb0c4d76d2d9f48bd
    Language: en-US
    Builddable map: 038a6194f65c4ef68885f6f16360dbc4.ditamap

commit f032a531bfa95cfe6cd5a046f2fd2a7d99b8a0a7
Author: REDACTED
Date:   Mon May 5 11:09:54 2025 +0000

    Update from SAP DITA CMS 2025-05-05 11:09:54

    Project: dita-all/bex1621329160251
    Project map: d3e749bbac3d4f728c12228db6629c45.ditamap

##################################################
[Remaining squash message was removed before commit...]

Author: ditaccms-bot

docs/sap-ai-core/consume-generic-secrets-in-executions-or-deployments-185a324.md

@@ -2,43 +2,43 @@
 
 # Consume Generic Secrets in Executions or Deployments
 
-Generic secrets at resource-group level can be attached to containers in executions or deployments. They can either be mounted as a volume or attached as an environment variable. The following examples illustrate how to consume a generic secret in a container by declaring it in the template. Note that only generic secrets can be attached to containers in this way. System secrets cannot be consumed in a template.
+Generic secrets at resource-group level can be attached to containers in executions or deployments. They can either be mounted as a volume or attached as an environment variable. The following examples illustrate how to consume a generic secret in a container by declaring it in the template. Note that only generic secrets can be attached to containers in this way. System secrets can't be consumed in a template.
 
 
 
 <a name="loio185a3245692542a78bfeff87220410c6__section_mjm_b1l_4rb"/>
 
 ## Consume a Generic Secret as an Environment Variable
 
-Generic secrets can be attached to containers using either `envFrom.secretRef` or `env.valueFrom.secretKeyRef`, as shown below.
+Generic secrets can be attached to containers using either `envFrom.secretRef` or `env.valueFrom.secretKeyRef`:
 
 -   Using `envFrom.secretRef`:
 
     ```
     spec:
-    	containers:
-    	- name: my-kserve-container
-    		image: centaur
-    		envFrom:
-    		- secretRef:
-    			name: MY_GENERIC_SECRET					
+      containers:
+      - name: my-kserve-container
+        image: centaur
+        envFrom:
+        - secretRef:
+          name: MY_GENERIC_SECRET					
     ```
 
-    If your secret contains invalid characters, such as hyphens \(-\), this method will result in error. You will need to map your secret to a valid variable name using `env.valueFrom.secretKeyRef`.
+    If your secret contains invalid characters, such as hyphens \(-\), this method results in error. In this case, map your secret to a valid variable name using `env.valueFrom.secretKeyRef`.
 
 -   Using `env.valueFrom.secretKeyRef`:
 
     ```
     spec:
-    	containers:
-    	- name: kserve-container
-    		image: centaur
-    		env:
-    		- name: MY_GENERIC_SECRET
-    		  valueFrom:
-    			secretKeyRef:
-    				name: my-generic-secret
-    				key: some-credential
+      containers:
+      - name: kserve-container
+        image: centaur
+        env:
+        - name: MY_GENERIC_SECRET
+          valueFrom:
+          secretKeyRef:
+            name: my-generic-secret
+            key: some-credential
     ```
 
 
@@ -48,21 +48,21 @@ Generic secrets can be attached to containers using either `envFrom.secretRef` o
 
 ## Consume a Generic Secret as a Volume Mount
 
-Generic secrets can also be mounted to containers as volumes, as shown below.
+Generic secrets can also be mounted to containers as volumes:
 
 ```
 spec:
-	containers:
-		- name: kserve-container
-		image: centaur	
-		volumeMounts:
-			- name: my-generic-secret
-			  mountPath: "/etc/my-generic-secret"
-			  readOnly: true
-	volumes:
-		- name: my-generic-secret
-		  secret:
-			secretName: my-generic-secret
+  containers:
+    - name: kserve-container
+    image: centaur  
+    volumeMounts:
+      - name: my-generic-secret
+        mountPath: "/etc/my-generic-secret"
+        readOnly: true
+  volumes:
+    - name: my-generic-secret
+      secret:
+      secretName: my-generic-secret
 ```
 
 
@@ -71,11 +71,11 @@ spec:
 
 ## Additional Information
 
-Secret names can be included as parameters in the templates and supplied via AI API configurations, as shown below.
+Secret names can be included as parameters in the templates and supplied via AI API configurations:
 
 ```
 envFrom:
 - secretRef:
-  name: "{{inputs.parameters.secretName}}"					
+  name: "{{inputs.parameters.secretName}}"
 ```
 

docs/sap-ai-core/create-a-prompt-template-declarative-815def5.md

@@ -64,7 +64,7 @@ The following formats are supported:
 -   The `additional_fields` field is unstructured and can be used to store metadata or configuration objects.
 
 
-Your template syncs automatically. After a few minutes, you'll be able to verify your template by sending a GET request to the endpoint `{{apiurl}}/lm/promptTemplates`.
+Your template syncs automatically. After a few minutes, you'll be able to verify your template by sending a GET request to the endpoint `{{apiurl}}/v2/lm/promptTemplates`.
 
 > ### Sample Code:  
 > ```

docs/sap-ai-core/create-a-prompt-template-imperative-92453a7.md

@@ -7,19 +7,19 @@
 ## Context
 
 > ### Recommendation:  
-> The imperative API supports full CRUD operations and is recommended for refining prompt templates in design time use cases. Iterations are tracked and can be viewed in the history endpoint.
+> The imperative API supports full CRUD operations and is recommended for refining prompt templates in design-time use cases. Iterations are tracked and can be viewed in the history endpoint.
 
 You can create a reusable prompt for a specific use case, including placeholders that are filled later.
 
 
 
 ## Procedure
 
-Create a prompt template by sending a POST request to endpoint <code><code>{{apiurl}}/lm/promptTemplates</code></code>.
+Create a prompt template by sending a POST request to endpoint <code><code>{{apiurl}}/v2/lm/promptTemplates</code></code>.
 
 > ### Sample Code:  
 > ```
-> curl -X POST "{{apiurl}}/lm/promptTemplates"\
+> curl -X POST "{{apiurl}}/v2/lm/promptTemplates"\
 > --header 'Content-Type: application/json' \
 > --header "Authorization: Bearer $TOKEN" \
 > --data '{
@@ -72,12 +72,12 @@ Create a prompt template by sending a POST request to endpoint <code><code>{{api
 
 ## Next Steps
 
-You can iterate over the prompt template, and make changes to it.
+You can iterate over the prompt template and make changes to it.
 
 You can save your changes as a new version. The latest iteration is always the head version and is marked with `isVersionHead: true`.
 
 > ### Tip:  
-> You'll need to update the version number when you want to create a new version, and the version entry must be semver compliant.
+> You'll need to update the version number when you want to create a new version, and the version entry must be compliant with semantic versioning \(SemVer\).
 
 You can check the change history for the template. For more information, see [Get Prompt Template History](get-prompt-template-history-dc204cf.md).
 

docs/sap-ai-core/delete-a-prompt-template-f7566e3.md

@@ -27,7 +27,7 @@ Delete a specific version of the prompt template, for imperatively managed promp
 
 ## Procedure
 
-Send a DELETE request to the endpoint `{{apiurl}}/lm/promptTemplates/{{promptTemplateId}}` and include the template ID of the prompt you want to delete.
+Send a DELETE request to the endpoint `{{apiurl}}/v2/lm/promptTemplates/{{promptTemplateId}}` and include the template ID of the prompt you want to delete.
 
 > ### Output Code:  
 > ```

docs/sap-ai-core/deploy-models-dd16e8e.md

@@ -145,15 +145,15 @@
 
 
 
-<a name="concept_z3s_f3h_vcc__d93e1165"/>
+<a name="concept_z3s_f3h_vcc__d94e1165"/>
 
 ## Optional Parameters
 
 The duration of a deployment can be limited using the `ttl` parameter. It takes an integer for quantity, and a single letter to specify units of time. Only minutes \(`m`\), hours \(`h`\) and days \(`d`\), are supported, and values must be natural numbers. For example, `"ttl": "5h"` gives the deployment a duration of 5 hours. `4.5h` and `4h30m` are not valid inputs. If no value is passed, the duration of the deployment if indefinite. Once the duration expires, the deployment is stopped and deleted.
 
 
 
-<a name="concept_z3s_f3h_vcc__d93e1196"/>
+<a name="concept_z3s_f3h_vcc__d94e1196"/>
 
 ## Deployment Quotas
 

docs/sap-ai-core/export-a-prompt-template-3acef9b.md

@@ -21,11 +21,11 @@ You can export a prompt template as a single file export in declarative compatib
 
 ## Procedure
 
-Send a GET request to the endpoint `{{apiurl}}/lm/promptTemplates/{{promptTemplateId}}/export`, and include the name of your file in the `output` parameter.
+Send a GET request to the endpoint `{{apiurl}}/v2/lm/promptTemplates/{{promptTemplateId}}/export`, and include the name of your file in the `output` parameter.
 
  > ### Sample Code:  
 > ```
-> curl -X GET "{{apiurl}}/lm/promptTemplates/{{promptTemplateId}}/export" \
+> curl -X GET "{{apiurl}}/v2/lm/promptTemplates/{{promptTemplateId}}/export" \
 > -Header "Authorization: Bearer <your_auth_token>" \
 > --output "exported_prompt_template.yaml"
 > ```

docs/sap-ai-core/get-a-prompt-template-bc8cead.md

@@ -28,17 +28,17 @@ Prompt templates can also be retrieved and consumed in orchestration. For more i
 
 ## Procedure
 
-Send a GET request to the endpoint `{{apiurl}}/lm/promptTemplates`, and include the information for your chosen retrieval method.
+Send a GET request to the endpoint `{{apiurl}}/v2/lm/promptTemplates`, and include the information for your chosen retrieval method.
 
 > ### Sample Code:  
 > ```
-> curl -X GET "{{apiurl}}/lm/promptTemplates?name=example-prompt-template&scenario=categorization&version=0.0.1" \
+> curl -X GET "{{apiurl}}/v2/lm/promptTemplates?name=example-prompt-template&scenario=categorization&version=0.0.1" \
 >   -Header "Authorization: Bearer <your_auth_token>"
 > ```
 
 > ### Sample Code:  
 > ```
-> curl -X GET "{{apiurl}}/lm/promptTemplates/{{promptTemplateId}}" \
+> curl -X GET "{{apiurl}}/v2/lm/promptTemplates/{{promptTemplateId}}" \
 > -Header "Authorization: Bearer <your_auth_token>"
 > ```
 

docs/sap-ai-core/get-prompt-template-history-dc204cf.md

@@ -12,11 +12,11 @@ You can list the history of edits to prompt templates, for imperatively managed
 
 ## Procedure
 
-Send a GET request to endpoint `{{apiurl}}/lm/scenarios/{{scenarioId}}/promptTemplates/{{promptTemplateName}}/versions/{{versionId}}/history` and include the name, scenario, and version of your prompt template.
+Send a GET request to endpoint `{{apiurl}}/v2/lm/scenarios/{{scenarioId}}/promptTemplates/{{promptTemplateName}}/versions/{{versionId}}/history` and include the name, scenario, and version of your prompt template.
 
  > ### Sample Code:  
 > ```
-> curl -X GET "{{apiurl}}/lm/scenarios/{{scenarioId}}/promptTemplates/{{promptTemplateName}}/versions/{{versionId}}/history" \
+> curl -X GET "{{apiurl}}/v2/lm/scenarios/{{scenarioId}}/promptTemplates/{{promptTemplateName}}/versions/{{versionId}}/history" \
 >   -Header "Authorization: Bearer <your_auth_token>"
 > ```
 

docs/sap-ai-core/images/Process_Flow_AI_Launchpad_to_AI_Core_d8dde1d.png

@@ -21,11 +21,11 @@ You can import a declarative prompt template as a single file export in yaml for
 
 ## Procedure
 
-Send a POST request to the endpoint `{{apiurl}}/lm/promptTemplates/import`, and include the name of your file in the `file` parameter.
+Send a POST request to the endpoint `{{apiurl}}/v2/lm/promptTemplates/import`, and include the name of your file in the `file` parameter.
 
  > ### Sample Code:  
 > ```
-> curl -X POST "{{apiurl}}/lm/promptTemplates/import" \
+> curl -X POST "{{apiurl}}/v2/lm/promptTemplates/import" \
 >      -Header "Authorization: Bearer <your_auth_token>" \
 >      -Header "Content-Type: multipart/form-data" \
 >      -File "file=@/path/to/your/file.yaml"