Shorten alt-text attributes to meet 150 character limit

Author: theresa-i

learn-pr/wwl-data-ai/create-ontology-with-fabric-iq/includes/2-evaluate-ontology-creation-approaches.md

@@ -8,7 +8,7 @@ Power BI semantic models organize data for business intelligence—they define t
 
 With this approach, you select an existing Direct Lake semantic model and Fabric IQ automatically generates entity types, properties, and relationship types. Each table becomes an entity type, columns become properties, and model relationships become relationship types.
 
-:::image type="content" source="../media/power-bi-semantic-model.png" alt-text="Screenshot of the Semantic model canvas showing five tables—vitalsignequipment, patients, rooms, departments, and hospitals—with relationship connectors between them." lightbox="../media/power-bi-semantic-model.png":::
+:::image type="content" source="../media/power-bi-semantic-model.png" alt-text="Screenshot of Semantic model canvas with five tables and relationship connectors between them." lightbox="../media/power-bi-semantic-model.png":::
 
 This automation saves significant setup time. Within minutes, you have working ontology structure ready to refine into business vocabulary.
 

learn-pr/wwl-data-ai/create-ontology-with-fabric-iq/includes/3-build-ontology-components-manually.md

@@ -20,7 +20,7 @@ To create an entity type, select **Add entity type** from the ontology ribbon. Y
 
 A hospital administrator thinks "Hospital"—not a technical table name. A care coordinator thinks "Patient"—not a database record. Choose names that make sense when spoken aloud: "Hospital contains Department" or "Patient assigned to Room."
 
-:::image type="content" source="../media/create-entity.png" alt-text="Screenshot of the ontology editor showing the Add entity type button in the ribbon at the top of the screen, with an empty canvas below and Entity Types pane on the left." lightbox="../media/create-entity.png":::
+:::image type="content" source="../media/create-entity.png" alt-text="Screenshot of ontology editor with Add entity type button in ribbon and Entity Types pane on left." lightbox="../media/create-entity.png":::
 
 The ribbon at the top contains all ontology actions. The Entity Types pane on the left lists each entity type as you create them, and the canvas in the center is where you see entity types and relationships laid out visually.
 
@@ -48,7 +48,7 @@ For each property, you make three critical decisions:
 
 You add properties for the Hospital entity type—HospitalName (string, static), City (string, static), State (string, static), and HospitalId (integer, static)—as shown in the image below. You select **Save** to create the properties.
 
-:::image type="content" source="../media/hospital-properties.png" alt-text="Screenshot of the Add properties dialog showing filled table with four rows: HospitalName (string, static), City (string, static), State (string, static), HospitalId (integer, static)." lightbox="../media/hospital-properties.png":::
+:::image type="content" source="../media/hospital-properties.png" alt-text="Screenshot of Add properties dialog with Hospital properties: HospitalName, City, State, and HospitalId." lightbox="../media/hospital-properties.png":::
 
 Each row in the dialog becomes a property on the Hospital entity type. Once saved, the properties appear in the Entity type configuration pane on the right.
 
@@ -62,7 +62,7 @@ To configure the entity type key, select **Add entity type key** in the Entity t
 
 Keys can only use string or integer properties—other data types don't work as identifiers. Keys are required before you can bind the entity type to data sources. Without a key, the system can't create instances from your source data.
 
-:::image type="content" source="../media/configured-properties.png" alt-text="Screenshot of the Entity type configuration pane showing Hospital entity type with Properties tab selected, listing properties HospitalName, City, State, HospitalId, and Entity type key section at bottom showing HospitalId configured as the key." lightbox="../media/configured-properties.png":::
+:::image type="content" source="../media/configured-properties.png" alt-text="Screenshot of Hospital entity type configuration showing properties list and HospitalId configured as the key." lightbox="../media/configured-properties.png":::
 
 You repeat this pattern for each business concept in your domain, for example, Department, Room, Patient. Each entity type gets business-friendly properties, appropriate data types, and a key, for instance,  identification.
 
@@ -78,7 +78,7 @@ To create a relationship type, select an entity type on the canvas (the visual w
 
 For a relationship from Hospital to Department, choose Hospital as the source entity and Department as the target entity. The direction matters—"Hospital contains Department" describes how hospitals organize, while "Department belongs to Hospital" describes the reverse perspective. Choose the direction that matches how people ask questions about your business.
 
-:::image type="content" source="../media/relationship-structure.png" alt-text="Screenshot of the Add relationship type dialog showing Source entity dropdown with Hospital selected, Target entity dropdown with Department selected, Name field with contains entered, and Add button at bottom." lightbox="../media/relationship-structure.png":::
+:::image type="content" source="../media/relationship-structure.png" alt-text="Screenshot of Add relationship dialog with Hospital as source and Department as target." lightbox="../media/relationship-structure.png":::
 
 Name the relationship type with business vocabulary that reads naturally: "Hospital contains Department" makes sense when you read source, relationship name, target together. Other examples: "Department has rooms" for Department to Room, or "Room has Patient" for Room to Patient. The name should describe what the relationship means, not just that a relationship exists.
 

learn-pr/wwl-data-ai/create-ontology-with-fabric-iq/includes/5-connect-ontology-to-data.md

@@ -75,7 +75,7 @@ To configure a time series data binding, follow the same steps as a static bindi
 
 Select **Timeseries** as the binding type, then choose the timestamp column—in this case, **Timestamp**. The interface then separates properties into two groups: **Static** (for the linking key, EquipmentId) and **Timeseries** (for the measured values, such as HeartRate and OxygenSaturation), as shown below.
 
-:::image type="content" source="../media/time-series-binding.png" alt-text="Screenshot showing the Configure data binding screen with Timeseries selected as the binding type, Timestamp chosen as the source data timestamp column, and properties divided into Static and Timeseries sections." lightbox="../media/time-series-binding.png":::
+:::image type="content" source="../media/time-series-binding.png" alt-text="Screenshot of Configure data binding with Timeseries type and properties divided into Static and Timeseries sections." lightbox="../media/time-series-binding.png":::
 
 The static property in a time series binding is the linking key—not a new static data binding, but the column that connects each reading back to its equipment entity. The timeseries properties are the measurements that update with each new reading.
 

learn-pr/wwl-data-ai/create-ontology-with-fabric-iq/includes/6-configure-relationships.md

@@ -30,7 +30,7 @@ For a *contains* relationship between Hospital and Department, the source table
 
 After selecting the table, select a **Source column** for each entity type—the column whose values match that entity type's key. For Hospital, select HospitalId. For Department, select DepartmentId, as shown below.
 
-:::image type="content" source="../media/relationship-configuration.png" alt-text="Screenshot showing the Relationship configuration pane showing LamnaHealthcareLH as the lakehouse, departments as the source table, Hospital with HospitalId mapped to its key, and Department with DepartmentId mapped to its key." lightbox="../media/relationship-configuration.png":::
+:::image type="content" source="../media/relationship-configuration.png" alt-text="Screenshot of Relationship configuration with departments table and HospitalId and DepartmentId mapped to entity keys." lightbox="../media/relationship-configuration.png":::
 
 Every row with values in both columns creates one relationship instance connecting those specific entities.
 

learn-pr/wwl-data-ai/create-ontology-with-fabric-iq/includes/7-preview-ontology.md

@@ -10,7 +10,7 @@ The entity type overview shows three sections for the selected entity type.
 
 **Entity instances table**—the list of actual instances populated from your bound data, showing RoomId, RoomNumber, DepartmentId, and RoomType for each room. Selecting any instance opens its detail view, showing that room's property values and its connections to other entities.
 
-:::image type="content" source="../media/preview-experience.png" alt-text="Screenshot showing the entity type overview for Room showing the relationship graph with VitalSignEquipment, Department, and Patient connections, property charts for RoomNumber, DepartmentId, and RoomType, and an entity instances table listing 10 rooms." lightbox="../media/preview-experience.png":::
+:::image type="content" source="../media/preview-experience.png" alt-text="Screenshot of Room entity overview with relationship graph, property charts, and entity instances table." lightbox="../media/preview-experience.png":::
 
 > [!NOTE]
 > When you first open the preview experience, you'll see an **"Updating your ontology"** message while the system processes your data in the background. After 1-2 minutes, refresh your browser to display the entity type overview.