Merge pull request #4897 from MicrosoftDocs/alt-period

Adding alt punctuation

Author: buck1ey

powerapps-docs/chatbots.md

@@ -13,7 +13,7 @@ ms.reviewer: mvakoc
 
 Power Virtual Agents allows you to quickly create and maintain intelligent chatbots using a no-code interface. App makers can create and manage their chatbots directly from [Power Apps](https://make.powerapps.com). 
 
-![Chatbots from Power Apps](media/chatbots.png "Chatbots from Power Apps")
+![Chatbots from Power Apps.](media/chatbots.png "Chatbots from Power Apps")
 
 You can create and manage your chatbots using the **Chatbots** option in the left navigation pane.
 

powerapps-docs/developer/component-framework/add-custom-controls-to-a-field-or-entity.md

@@ -19,7 +19,7 @@ Code components let you transform columns that traditionally contain text into v
 [!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
 
    > [!div class="mx-imgBorder"] 
-   > ![Custom slider control](../../maker/model-driven-apps/media/slider-control.PNG "Custom slider control ")
+   > ![Custom slider control.](../../maker/model-driven-apps/media/slider-control.PNG "Custom slider control ")
 
 ## Add a code component to a column
 
@@ -36,7 +36,7 @@ Following the steps below will change the default label and text box column of t
 5. On the Add Control page, select the component that you want, such as the **Linear Slider** component, and then select **Add**.
 
    > [!div class="mx-imgBorder"] 
-   > ![Add linear slider control](../../maker/model-driven-apps/media/add-slider.PNG "Add linear slider control")
+   > ![Add linear slider control.](../../maker/model-driven-apps/media/add-slider.PNG "Add linear slider control")
 
 6. Choose the client where you want the component to appear.
 
@@ -47,12 +47,12 @@ Following the steps below will change the default label and text box column of t
    - **Tablet**. To make the code component available on tablet devices running Dynamics 365 for tablets, select the Tablet option next to the component.
 
    > [!div class="mx-imgBorder"] 
-   > ![Choose the client apps to view the custom control](../../maker/model-driven-apps/media/choose-client.png "Choose the client apps to view the custom control") 
+   > ![Choose the client apps to view the custom control.](../../maker/model-driven-apps/media/choose-client.png "Choose the client apps to view the custom control") 
 
 7. Select the pencil icon next to **Min**, **Max**, and **Step**, set the property option, and then select **OK**.  
 
    > [!div class="mx-imgBorder"] 
-   > ![Add custom control properties](../../maker/model-driven-apps/media/ccf-add-properties.png "Add custom control properties")
+   > ![Add custom control properties.](../../maker/model-driven-apps/media/ccf-add-properties.png "Add custom control properties")
 
    - **Min**. Set the minimum accepted value. You can bind a static value that you enter or bind the value to an existing column. In this example **Bind to static value** is **Currency** and the minimum value that can be entered is *zero*.  
 
@@ -88,7 +88,7 @@ To add a code component like dataset component or simple table component to a gr
  Open a record that includes the column with the code component, such as the Opportunity form from the previous example, and view how the column is changed. The column is now rendered as a slider component instead of the text column.  
 
 > [!div class="mx-imgBorder"] 
-> ![Slider control rendered on form](../../maker/model-driven-apps/media/slider-control.PNG "Slider control rendered on form")  
+> ![Slider control rendered on form.](../../maker/model-driven-apps/media/slider-control.PNG "Slider control rendered on form")  
 
 ### See also
 

powerapps-docs/developer/component-framework/code-components-alm.md

@@ -44,7 +44,7 @@ When your code component is ready for testing inside a model-driven app, canvas
    The following diagram shows the one-to-many relationship between `cdsproj` and `pcfproj` projects:
 
     > [!div class="mx-imgBorder"]
-    > ![One-to-many relationship between cdsproj and pcfproj projects](media/code-component-projects.png "One-to-many relationship between cdsproj and pcfproj projects")
+    > ![One-to-many relationship between cdsproj and pcfproj projects.](media/code-component-projects.png "One-to-many relationship between cdsproj and pcfproj projects")
 
 More information: [Package a code component](import-custom-controls.md#package-a-code-component)
 
@@ -180,7 +180,7 @@ Reasons for adopting a segmented solution approach over a mixed single solution
 The following diagram shows an overview of the solution lifecycle for these two approaches:
 
 > [!div class="mx-imgBorder"]
-> ![Solution Strategies](media/solution-strategies.png "Solution Strategies")
+> ![Solution Strategies.](media/solution-strategies.png "Solution Strategies")
 
 The diagram describes the following points:
 
@@ -192,7 +192,7 @@ The diagram describes the following points:
 2. **Add existing code components** (after PAC CLI deployment) - If you are using the single solution approach, once deployed, the code component can be added to another solution (that must share the same solution publisher as used by the **PowerAppsTools** solution)
 
    > [!div class="mx-imgBorder"]
-   > ![Add Existing](media/add-existing.png "Add Existing")
+   > ![Add Existing.](media/add-existing.png "Add Existing")
    
 3. **Build unmanaged solution project** - If you are using solution `cdsproj` projects, then an unmanaged solution can be built using `msbuild`, and then imported into your development environment.
 
@@ -303,7 +303,7 @@ If you are using **AzureDevOps**, you can set your build pipeline versioning usi
 Consuming code components in canvas apps is different from model-driven apps. Code components must be explicitly added to the app by selecting  **Get more components** on the **Insert** panel. Once the code component is added to canvas app, it is included as the content inside the app definition. To update to a new version of the code component after it is deployed (and the control version incremented), the app maker must first open the app in Power Apps Studio and select **Update** when prompted on the **Update code components** dialog. The app must be then saved and published for the new version to be used when the app is played by users.
 
 > [!div class="mx-imgBorder"]
-> ![Update code components](media/upgrade-code-component.png "Update code components")
+> ![Update code components.](media/upgrade-code-component.png "Update code components")
 
 If the app is not updated or **Skip** is used, the app continues to use the older version of the code component even though it does not exist in the environment since it has been overwritten by the newer version. 
 

powerapps-docs/developer/component-framework/code-components-model-driven-apps.md

@@ -31,10 +31,10 @@ The [create your first code component](implementing-controls-using-typescript.md
 To add code components to a column or a table in model-driven apps, see [Add code components to model-driven apps](add-custom-controls-to-a-field-or-entity.md).
 
 > [!div class="mx-imgBorder"] 
-> ![Add linear slider control](../../maker/model-driven-apps/media/add-slider.PNG "Add linear slider control")
+> ![Add linear slider control.](../../maker/model-driven-apps/media/add-slider.PNG "Add linear slider control")
 
 > [!div class="mx-imgBorder"]
-> ![Data Set Grid component](media/add-dataset-component.png "Data Set Grid component")
+> ![Data Set Grid component.](media/add-dataset-component.png "Data Set Grid component")
 
 ## Update existing code components
 

powerapps-docs/developer/component-framework/community-resources.md

@@ -29,7 +29,7 @@ Make sure that you review the licensing terms and the source code before you dow
 > Code component run in the context of the end user who is using the component and can perform any action that may include accessing, capturing, and modifying the data. 
 
 > [!div class="mx-imgBorder"]
-> ![Component gallery](media/pcf-gallery.PNG "Components gallery")
+> ![Component gallery.](media/pcf-gallery.PNG "Components gallery")
 
 ## Videos        
 
@@ -83,12 +83,12 @@ There are two versions of the code component builder. Both of them are called **
 [PCF Builder for XrmToolBox](https://www.xrmtoolbox.com/plugins/Maverick.PCF.Builder/) provides a graphical user interface that lets you create code components in visual manner using Microsoft Power Platform CLI.
 
 > [!div class="mx-imgBorder"]
-> ![Component Builder in XrmToolBox](media/pcf-builder-xrmtoolbox.png "Component Builder in XrmToolBox")
+> ![Component Builder in XrmToolBox.](media/pcf-builder-xrmtoolbox.png "Component Builder in XrmToolBox")
 
 [PCF Builder extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=danish-naglekar.pcf-builder) provides a guided experience that not only lets  you create code components but you can preview code component inside of Visual Studio Code.
 
 > [!div class="mx-imgBorder"]
-> ![Component Builder in VS Code](media/pcf-builder-vscode.png "Component Builder in Visual Studio Code")
+> ![Component Builder in VS Code.](media/pcf-builder-vscode.png "Component Builder in Visual Studio Code")
 
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md

@@ -26,7 +26,7 @@ Professional developers can use Power Apps component framework to create, import
 
 When you open a canvas app that contains code components in Power Apps Studio, a warning message about potentially unsafe code appears. Code components in the Power Apps Studio environment have access to security tokens; hence only components from trusted sources should be opened. Administrators and system customizers should review and validate all code components before importing those components in an environment and making them available for makers to use in their apps. The `Default` publisher is shown when you import code components by using an unmanaged solution or when you have used `pac pcf push` to install your code component. 
 
-![Safety warning](media/canvas-app-safety-warning.png "Safety warning")  
+![Safety warning.](media/canvas-app-safety-warning.png "Safety warning")  
 
 ## Prerequisites
 
@@ -39,24 +39,24 @@ To add code components to an app, you need to enable the Power Apps component fr
 
 1. Sign in to [Power Apps](https://powerapps.microsoft.com/).
 
-2. Select **Settings** ![Settings](media/settings.png), and then select **Admin Center**.
+2. Select **Settings** ![Settings.](media/settings.png), and then select **Admin Center**.
 
     > [!div class="mx-imgBorder"]
-    > ![Settings and Admin Center](media/select-admin-center-from-settings.png "Settings and Admin Center") 
+    > ![Settings and Admin Center.](media/select-admin-center-from-settings.png "Settings and Admin Center") 
 
 3. On the left pane, select **Environments**, select the environment where you want to enable this feature, and then select **Settings**.
 
 4. On the **Products** tab, select **Features**.
 
    > [!div class="mx-imgBorder"]
-   > ![Enable Power Apps component framework](media/enable-pcf-feature.png "Enable Power Apps component framework")
+   > ![Enable Power Apps component framework.](media/enable-pcf-feature.png "Enable Power Apps component framework")
 
 5. From the list of available features, turn on **Power Apps component framework for canvas apps**, and then select **Save**.
 
 6. Now, open the app where you want to add the code component, got to **File** > **Settings**, and then select **Advanced settings**.
 
    > [!div class="mx-imgBorder"]
-   > ![Enable components for Power Apps component framework](media/enable-components-for-pcf.png "Enable components for Power Apps component framework")
+   > ![Enable components for Power Apps component framework.](media/enable-components-for-pcf.png "Enable components for Power Apps component framework")
    
 7. In the **Experimental features** section, turn on **Components**.
 
@@ -79,17 +79,17 @@ After you enable the Power Apps component framework feature in your environment,
 3. On the left pane, select **Add** (**+**), and then select **Get more components**. 
 
    > [!div class="mx-imgBorder"]
-   > ![Insert components](media/insert-code-components-using-get-more-components.png "Insert components")
+   > ![Insert components.](media/insert-code-components-using-get-more-components.png "Insert components")
 
 4. Select the **Code** tab, select a component from the list, and then select **Import**.<!--note from editor: Here and in step 5, I deleted "sample" because maybe the reader is adding a component they truly want, not necessarily a sample.-->
 
     > [!div class="mx-imgBorder"]
-    > ![Import a component](media/insert-component-add-sample-component.png "Import a component")
+    > ![Import a component.](media/insert-component-add-sample-component.png "Import a component")
 
 5. On the left pane, select **+**, expand **Code components**, and then select the component to add it to the app.
 
    > [!div class="mx-imgBorder"]
-   > ![Add a component](media/add-sample-component-from-list.png "Add a component")
+   > ![Add a component.](media/add-sample-component-from-list.png "Add a component")
 
    > [!NOTE]
    > You can also add components by selecting **Insert** > **Custom** > **Import component**. This option will be removed in a future release, so we suggest using the flow described above.<!--note from editor: Recommend deleting this unless there's a mechanism in place to revisit this topic in tandem with the future release. This is especially not a good candidate for note format, since it draws extra attention to this step that won't work before long.-->
@@ -98,7 +98,7 @@ After you enable the Power Apps component framework feature in your environment,
 On the **Properties** tab, you'll notice the code component properties are displayed. 
 
 > [!div class="mx-imgBorder"]
-> ![Default code component properties pane](media/property-pane-with-parameters.png "Default code components properties pane")
+> ![Default code component properties pane.](media/property-pane-with-parameters.png "Default code components properties pane")
 
 > [!NOTE]
 > Existing code components can be re-imported by updating the code component's manifest version if you want the properties to be available in the default **Properties** tab. As before, the properties will continue to be available on the **Advanced** properties tab.<!--note from editor: Edit okay? -->
@@ -110,7 +110,7 @@ On the **Properties** tab, you'll notice the code component properties are displ
 1. Next to the component, select **More** (**...**), and then select **Delete**.
 
    > [!div class="mx-imgBorder"]
-   > ![Delete a code component](media/delete-code-component.png "Delete a code component")
+   > ![Delete a code component.](media/delete-code-component.png "Delete a code component")
 
 1. Save the app to see the changes. 
 

powerapps-docs/developer/component-framework/custom-controls-overview.md

@@ -18,7 +18,7 @@ Code components are a type of solution component, which means they can be includ
 [!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
 
 > [!div class="mx-imgBorder"] 
-> ![Code components](media/code-components.gif "Code components")
+> ![Code components.](media/code-components.gif "Code components")
 
 Code components can be including into a solution and then imported into Microsoft Dataverse environment. Once the solution containing code components is imported, system administrators and system customizers can configure columns, subgrids, views, and dashboard subgrids to use in place of default components. You can add these code components to both **model-driven and canvas apps**.