Merge pull request SharePoint#8175 from dereklh7/Revert-6-13-WebParts

Validation: Added Unique Alt Text

Author: andrewconnell

docs/spfx/web-parts/guidance/supporting-section-backgrounds.md

@@ -1,7 +1,7 @@
 ---
 title: Supporting section backgrounds
 description: The available options for implementing support in your web parts for section backgrounds.
-ms.date: 06/16/2020
+ms.date: 06/13/2022
 ms.prod: sharepoint
 ---
 
@@ -13,11 +13,11 @@ Starting with SharePoint Framework v1.8, web parts can be made aware of any sect
 
 The section background color you can set is based upon the main color of the theme you applied. To set the background of a section open its properties:
 
-![Setting properties of a background](../../../images/supporting-section-backgrounds-modify-section.png)
+![Screenshot of a red arrow pointing to the background properties icon.](../../../images/supporting-section-backgrounds-modify-section.png)
 
 In the properties you can define which type of section background you want to set:
 
-![Setting properties of a background](../../../images/supporting-section-backgrounds-modify-section2.png)
+![Screenshot of the Layout options pane with the One column option being highlighted.](../../../images/supporting-section-backgrounds-modify-section2.png)
 
 ## Making your web part theme aware
 

docs/spfx/web-parts/guidance/use-existing-javascript-libraries.md

@@ -1,7 +1,7 @@
 ---
 title: Use existing JavaScript libraries in SharePoint Framework client-side web parts
 description: Ensure that your web parts won't negatively impact the performance of SharePoint pages that they're being used on.
-ms.date: 12/02/2020
+ms.date: 06/13/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -75,11 +75,11 @@ However, bundling existing JavaScript libraries with SharePoint Framework client
 
 When bundling existing JavaScript frameworks in the SharePoint Framework, all referenced scripts are included in the generated bundle file. Following the Angular example, an optimized web part bundle including Angular is over 170 KB.
 
-![Bundle file size highlighted in Explorer](../../../images/external-scripts-bundle-size.png)
+![Screenshot of the File Explorer screen's deploy folder showing the Hello World bundle JavaScript file being highlighted.](../../../images/external-scripts-bundle-size.png)
 
 If you add another web part to your project that also uses Angular and you build the project, you get two bundle files, one for each web part, each of them being over 170 KB.
 
-![Two bundle files highlighted in Explorer](../../../images/external-scripts-two-bundles-size.png)
+![Screenshot of the File Explorer screen's deploy folder showing two Hello World bundle JavaScript files being highlighted.](../../../images/external-scripts-two-bundles-size.png)
 
 If you add these web parts to a page, each user would download Angular multiple times, once with each web part on the page. This approach is inefficient and slows down page load time.
 
@@ -162,11 +162,11 @@ export default class HelloWorldWebPart extends BaseClientSideWebPart<IHelloWorld
 
 If you build your project now and take a look at the size of the generated bundle file, you notice that it's only 6 KB.
 
-![Bundle file size highlighted in Explorer](../../../images/external-scripts-external-angular-bundle-size.png)
+![Screenshot of File Explorer showing the deploy folder with the Hello Word JavaScript file being highlighted.](../../../images/external-scripts-external-angular-bundle-size.png)
 
 If you add another web part to your project that also uses Angular, and you build the project again, both bundles would be 6 KB each.
 
-![Two bundle files highlighted in Explorer](../../../images/external-scripts-external-angular-two-bundles-size.png)
+![Screenshot of File Explorer showing the deploy folder with two Hello Word JavaScript files being highlighted.](../../../images/external-scripts-external-angular-two-bundles-size.png)
 
 It isn't correct to assume that you've saved over 300 KB. Both web parts still need Angular and load it the first time the user visits the page where one of the web parts is placed.