docs(integration_cards_guidelines.md): Fix typos and improve grammar

Author: dimovpetar

resources/integration_cards_guidelines.md

@@ -2,19 +2,19 @@
 
 > *This document outlines the fundamental rules and best practices an AI agent must follow when developing or modifying Integration Cards. Adherence to these guidelines is critical for creating modern, maintainable, and performant UI Integration Cards.*
 ## 1. Coding Guidelines
-- **ALWAYS** attempt to make declarative Integration Card, such as "Calendar", "List", "Table", "Timeline", "Object" or "Analytical".
-  - in rare cases, you can also create Integration Card Extension.
+- **ALWAYS** strive to create declarative Integration Card, such as "Calendar", "List", "Table", "Timeline", "Object" or "Analytical".
+  - create an Integration Card Extension only in exceptional cases.
 - **ALWAYS** create links using the `actions` property.
 - **ALWAYS** refer to parameters using correct syntax - `{parameters>/parameterKey/value}`.
 - **ALWAYS** perform validation of the integration card as described in [2. Validation](#2-validation).
 - **ALWAYS** show a preview of the generated card following the [4. Preview Instructions](#4-preview-instructions).
 - **ALWAYS** generate new declarative integration cards using the `create_integration_card` tool.
 
 ### 1.1 Data
-- **NEVER** modify the given data under any circumstances
-- **ALWAYS** place service URL directly in the card manifest when provided
-- **ALWAYS** use destinations by their name when provided. Configure the destination in the `sap.card/configuration/destinations/` and reuse it with binding syntax like `{{destinations.destinationName}}`.
-- **NEVER** replace destination name with its URL
+- **NEVER** modify the provided data under any circumstances.
+- **ALWAYS** include the service URL directly in the card manifest when one is supplied.
+- **ALWAYS** reference destinations by name when available. Configure the destination in the `sap.card/configuration/destinations/` and reuse it with binding syntax like `{{destinations.destinationName}}`.
+- **NEVER** replace destination name with its URL.
 - **ALWAYS** place data configuration in: `"sap.card"/data/`
 - **NEVER** place data configuration in:
   - `"sap.card"/content/data/`
@@ -29,39 +29,38 @@
   - `"sap.card"/header/data/path` (Header-specific path. It overrides the primary data path)
 
 #### 1.1.1 Data Errors Detection
-- Symptom: "No data to display" message appears
+- Symptom: "No data to display" message appears.
 - Cause: Incorrect data configuration or data path in the content incorrectly overrides the primary data path.
-- Solution: Verify all rules in [1.1 Data](#11-data) are properly followed
+- Solution: Verify all rules in [1.1 Data](#11-data) are properly followed.
 
 ### 1.2 Internationalization
-- **ALWAYS** bind properties that are not bound to the data to the `i18n` model
+- **ALWAYS** bind properties that are not bound to the data to the `i18n` model.
 
 ### 1.3 Analytical Cards
 - **ALWAYS** follow [6. Analytical Cards Coding Guidelines](#6-analytical-cards-coding-guidelines) when developing Analytical cards.
 
 ## 2. Validation
 - **ALWAYS** ensure that `manifest.json` file is valid JSON.
 - **ALWAYS** ensure that in `manifest.json` file the property `sap.app/type` is set to `"card"`.
-- **ALWAYS** avoid deprecated properties in `manifest.json` and other places.
-- **NEVER** treat Integration Cards project as UI5 project, except for cards of type "Component".
+- **ALWAYS** avoid using deprecated properties in `manifest.json` and elsewhere.
+- **NEVER** treat Integration Cards' project as UI5 project, except for cards of type "Component".
 
 ## 3. Card Explorer
-- Contains detailed description for every property in the Integration Cards Schema, integration of cards in hosting environments, examples, configuration editor documentation and examples, and many more broader topics and best practices,
-- can be found at https://ui5.sap.com/test-resources/sap/ui/integration/demokit/cardExplorer/webapp/index.html
+- The Card Explorer provides detailed documentation for the Integration Cards schema, including descriptions of every property, guidance for integrating cards into hosting environments, configuration editor documentation with examples, and broader best practices. It is available at: https://ui5.sap.com/test-resources/sap/ui/integration/demokit/cardExplorer/webapp/index.html
 
 ## 4. Preview Instructions
-- **ALWAYS** search the existing card folder for preview instructions or scripts and use them, if available.
+- **ALWAYS** check the card folder for an existing preview file and any accompanying instructions or scripts, and reuse them if available.
   * for example, in NodeJS-based projects, search the `package.json` file for `start` or similar script. If such is available, use it
   * also search in the `README.md` file.
-- If preview instructions are not available, you have to create an html page, that contains a `ui-integration` card element that uses the card manifest. Then serve the html page using `http` server.
+- If preview instructions are not available, you have to create an HTML page that contains a `ui-integration` card element which references the card manifest. Then serve the HTML page using `http` server.
 
 ## 5. Configuration Editor
-- When there is Configuration Editor, always try to make most of the integration card fields editable.
+- When a Configuration Editor is available, make as many Integration Card fields editable as possible.
 
 ## 6. Analytical Cards Coding Guidelines
 - **ALWAYS** set `sap.card/content/chartType` property.
-- **ALWAYS** adjust `sap.card/content/measures`, `sap.card/content/dimensions` and `sap.card/content/feeds` based on the `sap.card/content/chartType` property and data structure. This is critical for proper data display.
-- **ALWAYS** use `sap.card/content/chartProperties` to adjust labels, colors, the legend, and other thing of the chart.
+- **ALWAYS** adjust `sap.card/content/measures`, `sap.card/content/dimensions` and `sap.card/content/feeds` to match the `sap.card/content/chartType` property and data structure. This is critical for proper data display.
+- **ALWAYS** use `sap.card/content/chartProperties` to adjust labels, colors, the legend, and other chart aspects.
 - **ALWAYS** define each feed with its type (Dimension or Measure), its unique identifier (uid), and the associated values using defined measures and dimensions. Example:
 ```json
 "feeds": [
@@ -81,7 +80,7 @@
   }
 ]
 ```
-- **ALWAYS** ensure that the uid in feeds accurately matches the required UID for your chosen chartType (e.g., color, size, dataFrame).
+- **ALWAYS** ensure the `uid` in `feeds` exactly matches the UID required for the selected chartType (e.g., color, size, dataFrame).
 
 ### 6.1 Comprehensive List of All Chart Types, UIDs and Examples