update // power apps portals deprecation

pages/power-apps-portals-deprecations.txt

@@ -1,9 +1,6 @@
 Important upcoming changes and deprecations in Power Pages
 
-
-Article														  06/26/2024  
-																	9 contributors
-															FeedbackIn this article
+  Article  06/26/2024  9 contributorsFeedbackIn this article
 
 The announcements for changes and deprecations described in this article apply to Power Pages. Makers, developers, and IT pros can use this information to prepare for future releases.
 
@@ -17,11 +14,11 @@ In July 2024, we're introducing improvements to the way text, image, and button
 
 We'll also change the way button components are created. Previously, buttons were represented using the <button> HTML tag with URLs handled by the onclick attribute: 
 
-<button onclick="window.location.href='/page/subpage-1/'" type="button" value="subpage-1" class="button1">Add a call to action here</button>
+<button onclick="window.location.href='/page/subpage-1/'" type="button" value="subpage-1" class="button1">Add a call to action here</button>
 
 With the upcoming improvements, all new button components are created using the <a> anchor tag, with the href attribute responsible for URL navigation. Any <a> tag with the btn class are recognized as a button component in design studio:
 
-<a href="/page/subpage-1/" class="btn button1">Add a call to action here</a>
+<a href="/page/subpage-1/" class="btn button1">Add a call to action here</a>
 
 This change only applies to new buttons. Buttons that were previously created aren't impacted and continue to work in design studio. However, you might need to adjust any custom CSS or JavaScript that uses the <button> tag for selection.