updates

Author: mduelae

powerapps-docs/maker/canvas-apps/code-view.md

@@ -31,7 +31,7 @@ With code view you can:
 
 Code view shows the code for the selected control and all its child controls.
 
-Code view lets you copy and paste code to any screen in your app, or outside of Power Apps, to duplicate the control. This duplication feature is helpful when controls are highly customized and you want to share or duplicate it.
+Code view lets you copy and paste code to any screen in your app or outside of Power Apps to duplicate the control. This feature is helpful when controls are highly customized and you want to share or duplicate them.
 
 ### View code
 
@@ -46,19 +46,19 @@ Code view lets you copy and paste code to any screen in your app, or outside of
 
 ### Copy and paste code
 
-1. To copy the code of a selected control, you can:
+1. To copy the code of a selected control:
    - Use the menu to copy.
-   - Use the shortcut "ctrl + c"
+   - Use the shortcut <kbd>Ctrl</kbd>+<kbd>C</kbd>.
    - When viewing your code in the code view popup, select **Copy code**.
 1. To add a new control from the code:
 
-   - Use the menu to paste.
-   - Use the shortcut "ctrl + v"
+- Use the menu to paste.
+- Use the shortcut <kbd>Ctrl</kbd>+<kbd>V</kbd>.
 
    :::image type="content" source="media/code-view/paste-code.png" alt-text="Screenshot of the tree view in Power Apps Studio, with the Paste code option highlighted on a control's context menu.":::
 
 > [!IMPORTANT]
-> You must use the YAML format that Power Apps Studio generates. The code is validated before the new control is created.
+> Use the YAML format that Power Apps Studio generates. The code is validated before the new control is created.
 
 ## Known limitations
 

powerapps-docs/maker/canvas-apps/power-apps-yaml.md

@@ -17,13 +17,12 @@ ms.custom:
 
 # View source code files for canvas apps
 
-You can use the source code for a canvas app to review changes made my makers in Power Apps Studio. The generated canvas app YAML code is read-only and shouldn't be modified. Any change in the file will be ignored and can be lost.
+Use the source code for a canvas app to review changes made by makers in Power Apps Studio. The generated canvas app YAML code is read-only and can't be modified. Any changes to the file are ignored and might be lost.
 
-> [!NOTE]
-> - The YAML schema is in active development, the content may be incomplete.
-> - The current static schema for ***.pa.yaml** files can be found, [here](https://raw.githubusercontent.com/microsoft/PowerApps-Tooling/refs/heads/master/schemas/pa-yaml/v3.0/pa.schema.yaml).
+> - The YAML schema is in active development, and the content might be incomplete.
+> - The current static schema for ***.pa.yaml** files is available [here](https://raw.githubusercontent.com/microsoft/PowerApps-Tooling/refs/heads/master/schemas/pa-yaml/v3.0/pa.schema.yaml).
 
-We use Power Fx and YAML as the languages for Power Apps source code. YAML is appreciated for its human-readable format and benefits from a wide array of existing editors, tools, and libraries for its manipulation.
+Power Fx and YAML are the languages used for Power Apps source code. YAML is valued for its human-readable format and benefits from a wide array of editors, tools, and libraries for manipulation.
 
 ## Access source code files
 
@@ -32,7 +31,7 @@ You have access to the source code files if you're using the [Dataverse Git Inte
 The Power Apps Studio creates the source code for canvas apps, which is stored as *.pa.yaml files within the **.msapp** file. The **.msapp** file is a binary file that contains a collection of files, including the source code.
 
 > [!TIP]
-> To effectively use ALM, it's recommended to use solutions. [Canvas apps package](export-import-app-package.md) doesn't support ALM and should only be used for basic import and export capabilities when Dataverse isn't available.
+> To effectively use application lifecycle management (ALM), it's recommended to use solutions. [Canvas apps package](export-import-app-package.md) doesn't support ALM and should only be used for basic import and export capabilities when Dataverse isn't available.
 
 You can also get the source code files either from the **.msapp** file or by using [Power Platform CLI](/power-platform/developer/cli/introduction).
 
@@ -78,36 +77,35 @@ Only ***.pa.yaml** files within the **\src** folder can be used as source code.
 
 ## Power Apps YAML schema versions
 
-Currently there are three schema versions of Power Apps Source Code:
+Currently, there are three schema versions of Power Apps source code:
 
-|Format Name|File Extension|Description|
+|Format name|File extension|Description|
 |-----------|-----------|-------|
-| [Experimental](power-apps-yaml.md#experimental-format-fxyaml) | *.fx.yaml| Version used by the experimental [Power Apps Git version control](git-version-control.md)  and [pac canvas unpack](/power-platform/developer/cli/reference/canvas#pac-canvas-unpack) - no longer in development.|
-| [Early Preview](power-apps-yaml.md#early-preview) | -  | The version used by code view, copy code, and paste code. There's no version information in this schema, therefore it isn't suitable for version control. When [code view](code-view.md) is generally available (GA), it switches to the source code preview format.|
-| [Source Code](power-apps-yaml.md#source-code-payaml) | *.pa.yaml files | Includes enhancements and version details for source control and it is in active development. |
+| [Experimental](power-apps-yaml.md#experimental-format-fxyaml) | *.fx.yaml| Version used by the experimental [Power Apps Git version control](git-version-control.md) and [pac canvas unpack](/power-platform/developer/cli/reference/canvas#pac-canvas-unpack)—no longer in development.|
+| [Early preview](power-apps-yaml.md#early-preview) | -  | The version used by code view, copy code, and paste code. There's no version information in this schema, so it isn't suitable for version control. When [code view](code-view.md) is generally available (GA), it switches to the source code preview format.|
+| [Source code](power-apps-yaml.md#source-code-payaml) | *.pa.yaml files | Includes enhancements and version details for source control and is in active development. |
 
 ## Experimental format (*.fx.yaml)
 
-This schema represents an experimental format employed by the Power Platform CLI to process and convert canvas apps into a source code format. However, this format is no longer being actively developed.
+This schema describes an experimental format used by the Power Platform CLI to process and convert canvas apps into a source code format. This format isn't actively developed anymore.
 
-You can't directly convert ***.fx.yaml** files to the new formats. To convert older apps, you need to package the canvas app as a **.msapp** file and import it into Power Apps Studio.
+You can't directly convert ***.fx.yaml** files to the new formats. To convert older apps, package the canvas app as a **.msapp** file and import it into Power Apps Studio.
 
 ## Preview
 
-This version is used by [Code view](code-view.md) during the [preview](working-with-experimental-preview.md#preview) period. It is designed to create canvas apps in Power Apps Studio, allowing you easily copy and paste controls. In this version, the source code is used in Power Apps Studio instead of being converted (like the experimental format).
+This version is used by [Code view](code-view.md) during the [preview](working-with-experimental-preview.md#preview) period. It is designed to create canvas apps in Power Apps Studio, letting you easily copy and paste controls. In this version, the source code is used in Power Apps Studio instead of being converted, like the experimental format.
 
-The format during the preview was temporary and it is no longer in use. You can paste code from the preview format.
+The format during the preview was temporary and is no longer in use. You can paste code from the preview format.
 
 Here are the changes made from the experimental format:
 
-1. **ZIndex Property Removal**: The ZIndex property is removed. Instead, a screen is now represented as an array of controls. The order of controls now determines their stacking order. Normal controls are ordered in ascending order, while responsive controls are ordered in descending order.
-1. **JSON Object Representation Replacement**: We no longer use the "As" syntax to define the control type. Instead, the left side of the control's name identifier remains unique. Only properties that differ from the default values are serialized. Two new properties are added to define the control type and default values:
+1. **ZIndex property removal**: The ZIndex property is removed. Instead, a screen is represented as an array of controls. The order of controls determines their stacking order. Normal controls are ordered in ascending order, while responsive controls are ordered in descending order.
+1. **JSON object representation replacement**: The "As" syntax is no longer used to define the control type. Instead, the left side of the control's name identifier remains unique. Only properties that differ from the default values are serialized. Two new properties define the control type and default values:
 
 - **Control**: Represents the control type in YAML.
-- **Variant**: Identifies a variant of a control type, which might alter default property values, add or remove properties, or modify the behavior/layout of the control.
+- **Variant**: Identifies a variant of a control type, which might alter default property values, add or remove properties, or modify the behavior or layout of the control.
 
 These properties are used for instantiating controls and don't accept Power Fx expressions.
-
 ## Source code (*.pa.yaml)
 
 > [!IMPORTANT]