fix: improve v3 and documentation text

Author: matthiashader

BREAKING_CHANGES.md

@@ -12,4 +12,4 @@ Please select your target version
 
 ## Questions ❓🙋‍♀️
 
-If you have further questions or you are facing any problems during migration please [contact us over our forum](https://community.siemens.com/c/ix/).
+If you have any further questions, or you encounter any issues during the migration, please [contact us over our forum](https://community.siemens.com/c/ix/).

BREAKING_CHANGES/v3.md

@@ -4,27 +4,27 @@
 
 The `@siemens/ix-icons` package requires manual bootstrapping. For detailed installation instructions, please refer to the [`@siemens/ix-icons`](https://github.com/siemens/ix-icons) repository.
 
-If you are using one of the framework wrappers like `@siemens/ix-angular`, `@siemens/ix-react` or `@siemens/ix-vue` see sections below.
+If you are using one of the framework wrappers such as `@siemens/ix-angular`, `@siemens/ix-react` or `@siemens/ix-vue` refer to the sections below.
 
 ### Usage of icons inside `@siemens/ix-react` and `@siemens/ix-vue` changed
 
-Icon imports by name (e.g. `<IxIcon name="star" />`) are not supported by default any more.
+Icon imports by name (e.g. `<IxIcon name="star" />`) are no longer supported by default.
 
-Do the import of the icon
+To import the icon, use the following statement:
 
 ```ts
 import { iconStar } from '@siemens/ix-icons/icons';
 ```
 
-Use the icon as attribute assertion
+Use the icon as attribute like this:
 
 ```html
 <IxIcon name="{iconStar}" />
 ```
 
-If you want to use the "legacy" style (`<IxIcon name="star" />`) you have do some setup tasks.
+If you want to use the "legacy" style (`<IxIcon name="star" />`), you'll need to do some additional setup tasks.
 
-Create a copy task to ensure that all icons from the `@siemens/ix-icons` package is available as a static resource. Example of a vite config (build only) example:
+Create a copy task to ensure that all icons from the `@siemens/ix-icons` package are available as a static resource. Below is an example of a vite configuration (build only) example:
 
 ```ts
 export default defineConfig({
@@ -45,7 +45,7 @@ export default defineConfig({
 
 ### Usage of icons inside `@siemens/ix-angular` changed
 
-To use imports by name (e.g. `<ix-icon name="star"></ix-icon>`) an additional configuration entry is required inside of `angular.json`:
+To use imports by name (e.g. `<ix-icon name="star"></ix-icon>`), you need to add a configuration entry inside of `angular.json`:
 
 ```json
 "assets": [
@@ -89,11 +89,11 @@ To configure the asset path from which domain the `ix-icon` component will load
 <IxIcon name="star"></IxIcon>
 ```
 
-Will fetch the svg from `https://some-resource-domain/star.svg`
+Above will fetch the svg from `https://some-resource-domain/star.svg`
 
 #### with `setAssetPath`-function
 
-Ensure to call the `setAssetPath`-function before using the `IxIcon` component e.g in the main file.
+Make sure to call the `setAssetPath`-function before using the `IxIcon` component, such as in the main file.
 
 ```ts
 import { setAssetPath } from '@siemens/ix-icons/components';
@@ -105,9 +105,9 @@ setAssetPath('https://some-resource-domain');
 <IxIcon name="star"></IxIcon>
 ```
 
-Will fetch the svg from `https://some-resource-domain/star.svg`
+Above will fetch the svg from `https://some-resource-domain/star.svg`
 
-This will preload all icons without providing the SVGs as assets. The downside of doing this that it results in a larger bundle size. **not recommended**
+This will preload all icons without including the SVGs as assets, which results in a larger bundle size. This approach ist **NOT recommended**.
 
 ## Change props to `@internal`: