Merge pull request #5023 from PatrickFarley/aoai-build

Aoai build

Author: prmerger-automator[bot]

articles/ai-foundry/what-is-azure-ai-foundry.md

@@ -70,7 +70,7 @@ The left pane is organized around your goals. Generally, as you develop with Azu
 * **Define and explore**. In this stage you define your project goals, and then explore and test models and services against your use case to find the ones that enable you to achieve your goals.
 * **Build and customize**. In this stage, you're actively building solutions and applications with the models, tools, and capabilities you selected. You can also customize models to perform better for your use case by fine-tuning, grounding in your data, and more. Building and customizing might be something you choose to do in the Azure AI Foundry portal, or through code and the Azure AI Foundry SDKs. Either way, a project provides you with everything you need.
   * Once you're actively developing in your project, the **Overview** page shows the things you want easy access to, like your endpoints and keys.
-* **Assess and improve**. In this stage, you're looking for where you can improve your application's performance. You might choose to use tools like tracing to debug your application or compare evaluations to hone in on how you want your application to behave. You can also integrate with safety & security systems so you can be confident when you take your application to production.
+* **Observe and improve**. In this stage, you're looking for where you can improve your application's performance. You might choose to use tools like tracing to debug your application or compare evaluations to hone in on how you want your application to behave. You can also integrate with safety & security systems so you can be confident when you take your application to production.
 
 If you're an admin, or leading a development team, and need to manage the team's resources, project access, quota, and more, you can do that in the Management Center.
 

articles/ai-services/openai/how-to/dall-e.md

@@ -259,22 +259,23 @@ Replace the following values:
 - `<api_version>` is the version of the API you want to use. For example, `2025-04-01-preview`.
 
 **Required headers**:
-- `Content-Type`: `application/json`
+- `Content-Type`: `multipart/form-data`
 - `api-key`: `<your_API_key>`
 
 **Body**:
 
 The following is a sample request body. You specify a number of options, defined in later sections.
 
-```json
-{
-    "image": "<base64_encoded_image>",
-    "prompt": "Add a beach ball in the center.",
-    "model": "gpt-image-1",
-    "size": "1024x1024", 
-    "n": 1,
-    "quality": "high"
-}
+> [!IMPORTANT]
+> The Image Edit API takes multipart/form data, not JSON data. The example below shows sample form data that would be attached to a cURL request.
+
+```
+-F "image[][email protected]" \
+-F 'prompt=Add a beach ball in the center' \
+-F "model=gpt-image-1" \
+-F "size=1024x1024" \
+-F "n=1" \
+-F "quality=high"
 ```
 
 ### Output
@@ -304,7 +305,7 @@ The *image* value indicates the image file you want to edit. It can be either a
 
 #### Mask
 
-The *mask* parameter is the same type as the main *image* input parameter. It defines the area of the image that you want the model to change, using fully transparent pixels (alpha of zero) in those areas. The mask can be a URL or base 64-encoded image data. It must be a PNG file and have the same dimensions as the image.
+The *mask* parameter is the same type as the main *image* input parameter. It defines the area of the image that you want the model to edit, using fully transparent pixels (alpha of zero) in those areas. The mask must be a base 64-encoded image. It must be a PNG file and have the same dimensions as the input image.
 
 
 #### [DALL-E 3](#tab/dalle-3)