Removing summary section

Author: Karuna-Mendix

content/en/docs/partners/altair/altair-graph-studio.md

@@ -95,11 +95,17 @@ You now have a graph ontology in Altair Graph Studio with data and a SPARQL quer
 
 Altair Graph Studio allows you to do much more, such as ingesting data from data lakes or APIs and linking siloed data into one unified ontology, but for now you can focus on this basic graph.
 
-## Exposing the Data via an OData REST Endpoint
+## Exposing Graph Data in the Mendix Application
+
+Altair Graph Studio (AGS) allows you to store and retrieve graph data structures. Using either OData REST endpoints or SPARQL queries via the SPARQL API endpoint, you can retrieve this data into your Mendix application.
+
+The OData approach provides the easiest integration with automatic entity mapping and association handling, while the SPARQL approach offers more control for complex graph queries. Both methods enable you to build powerful applications that leverage the scalability and flexibility of graph databases. 
+
+### Exposing the Data via an OData REST Endpoint
 
 The simplest way to use Graph data in a Mendix application is by using an OData endpoint. In Altair Graph Studio, you can export an entire graph via OData. This will create an OData endpoint allowing flexible OData queries on the data in your graph database.
 
-### Create an OData API in Graph Studio
+#### Creating an OData API in Graph Studio
 
 Create a new OData API in your graphmart. To do this, follow the steps below.
 
@@ -121,7 +127,7 @@ Create a new OData API in your graphmart. To do this, follow the steps below.
 
 4. To see the contract of the endpoint, use the endpoint URL displayed in the endpoint configuration page under **ODBC (SQL)** and append `/$metadata` to this URL. You will need it when using the endpoint in Studio Pro.
 
-### Use the OData Endpoint in a Mendix Project
+#### Using the OData Endpoint in a Mendix Project
 
 Add a [consumed OData service](/refguide/consumed-odata-service/) in your project by opening Studio Pro and right-clicking your module > **Add other** > **Consumed OData service**. In the **Add Consumed OData Service** dialog, provide the location of the endpoint `$metadata` contract, as well as your username and password credentials. Studio Pro will read the contract to determine all the entities and actions provided by this endpoint.
 
@@ -131,29 +137,29 @@ In the consumed OData service document, you can provide configuration for the en
 
 {{< figure src="/attachments/partners/altair/howto-ags/ags-22.png" class="no-border" >}}
 
-### Create External Entities for Datasets from the OData Endpoint
+#### Creating External Entities for Datasets from the OData Endpoint
 
 The [Integration pane](/refguide/integration-pane/) in the right column displays all the graph classes exposed via the OData REST API. You can see the attributes (properties) of these classes and the associations. The Integration pane also shows the capabilities of the data provided by the endpoint. In this example, all the data is read-only, as the Altair Graph Database only provides read-only access to the data.
 
 Select which classes you need for your application and drag and drop them into a domain model. Here, they will be displayed as purple external entities. This indicates that the data is available to your application but is retrieved from an external service (in this case, the Altair Graph Database).
 
 {{< figure src="/attachments/partners/altair/howto-ags/ags-23.png" class="no-border" >}}
 
-### Build Pages Using External Entities
+#### Building Pages Using External Entities
 
 You can use these external entities in your pages and microflows similarly to persistent entities. For this example, create your overview pages by right-clicking the entity and selecting **Generate overview pages**. 
 
 {{< figure src="/attachments/partners/altair/howto-ags/ags-24.png" class="no-border" >}}
 
-### Run the Application and Test
+#### Running the Application and Test
 
 You can now start the application and test the results. Whenever you open a page using external entities from the Integration pane, the data will automatically be retrieved from Altair Graph Studio via an OData REST call.
 
 {{< figure src="/attachments/partners/altair/howto-ags/ags-25.png" class="no-border" >}}
 
 Filtering, sorting, and pagination are automatically done server-side by your graph database. This is essential for large datasets to avoid overloading the front-end with too many objects.
 
-### Lazy-Loaded Tree Widget
+#### Lazy-Loaded Tree Widget
 
 Altair Graph Studio automatically provides associations for linked entities in your graph. These graph associations are part of the OData endpoint and part of your external entities. When you drag your OData datasets into your domain model, the resulting external entities will show associations from the OData endpoint.
 
@@ -165,11 +171,11 @@ This is done automatically when you set the external entities as the data source
 
 {{< figure src="/attachments/partners/altair/howto-ags/ags-27.png" class="no-border" >}}
 
-## Query SPARQL in Mendix
+### Query SPARQL in Mendix
 
 If you need full control over your graph queries, you can use [consumed REST services](/refguide/consumed-rest-service/) to execute SPARQL queries in your graph database.
 
-### Configuring the REST Call
+#### Configuring the REST Call
 
 Run SPARQL queries from Mendix by using the SPARQL API in Altair Graph Studio. To do this, follow the steps below.
 
@@ -198,7 +204,7 @@ Run SPARQL queries from Mendix by using the SPARQL API in Altair Graph Studio. T
 
     {{< figure src="/attachments/partners/altair/howto-ags/ags-8.png" class="no-border" >}}
 
-### Microflow to Execute the SPARQL Query
+#### Microflow to Execute the SPARQL Query
 
 Define a microflow that will execute the API call with the SPARQL query and return the resulting data as an entity list. In this example, the endpoint is defined using two constants:
 
@@ -209,13 +215,13 @@ By using constants, you can override these on deployment to match the environmen
 
 {{< figure src="/attachments/partners/altair/howto-ags/ags-13.png" class="no-border" >}}
 
-### Customers Overview Page
+#### Customers Overview Page
 
 Create a page that will show the retrieved data. This example uses a [Data Grid 2](/appstore/modules/data-grid-2/) with a microflow data source. The microflow data source is configured to use the microflow that was created in the previous step.
 
 {{< figure src="/attachments/partners/altair/howto-ags/ags-14.png" class="no-border" >}}
 
-### Test the Result
+#### Testing the Result
 
 You can now run your application to validate the result. It should have a data grid showing all objects and a detail form showing the details of one specific object, as seen below:
 
@@ -224,9 +230,3 @@ You can now run your application to validate the result. It should have a data g
 You should also see detail pages that show data from a single concept in your graph database:
 
 {{< figure src="/attachments/partners/altair/howto-ags/ags-16.png" class="no-border" >}}
-
-## Summary
-
-As illustrated, Altair Graph Studio (AGS) allows you to store and retrieve graph data structures. Using either OData REST endpoints or SPARQL queries via the SPARQL API endpoint, you can retrieve this data into your Mendix application.
-
-The OData approach provides the easiest integration with automatic entity mapping and association handling, while the SPARQL approach offers more control for complex graph queries. Both methods enable you to build powerful applications that leverage the scalability and flexibility of graph databases.