some more things

Author: Jay-o-Way

CONTRIBUTING.md

@@ -27,8 +27,8 @@ Another great way to help is by voting and commenting on feature proposals:
 
 ### Proposing new public APIs or UI
 
-Please follow the [New Feature or API Process](docs/feature_proposal_process.md) before adding, removing, or changing public APIs or UI.  
-All new public APIs, new UI, or breaking changes to existing features **must*- go through that process before submitting code changes.  
+Please follow the [New Feature or API Process](docs/feature_proposal_process.md) before adding, removing, or changing public APIs or UI.
+All new public APIs, new UI, or breaking changes to existing features **must** go through that process before submitting code changes.
 You don't need to follow that process for bug fixes or other small changes.
 
 ### Contribution bar
@@ -63,11 +63,11 @@ file in the repository, as needed.
 
 ## Documentation and usage samples
 
-You can also read and contribute to the WinUI documentation here: <https://learn.microsoft.com/uwp/toolkits/winui>
+You can also read and contribute to the WinUI documentation here: [WinUI documentation](https://learn.microsoft.com/uwp/toolkits/winui)
 
-You can find usage examples of the controls available in WinUI in the WinUI 3 Gallery app: <https://github.com/Microsoft/WinUI-Gallery/>  
+You can find usage examples of the controls available in WinUI in the WinUI 3 Gallery app: [WinUI 3 Gallery app](https://github.com/Microsoft/WinUI-Gallery/)  
 
-Which can also be installed from the Microsoft Store: <https://apps.microsoft.com/detail/9p3jfpwwdzrc>
+Which can also be installed from the Microsoft Store: [Microsoft Store](https://apps.microsoft.com/detail/9p3jfpwwdzrc)
 
 ## API spec discussions
 

CONTRIBUTING_feedback_and_requests.md

@@ -30,31 +30,31 @@ Try this:
 ### Features
 
 - It's very helpful to specify the "why" behind your request, even if it seems obvious. Comparisons can help, but shouldn't replace explanation.
-- Example: "I need `<`feature`>` so that I can achieve `<`goal`>`. Otherwise, I have to `<`alternative`>`."
+- Example: "I need \<feature\> so that I can achieve \<goal\>. Otherwise, I have to \<alternative\>."
 
   There are also usually great opportunities to have feature-related impact in our [spec repo](https://github.com/microsoft/microsoft-ui-xaml-specs/tree/master). Here, you can give direct feedback and help shape the new features and APIs that we're currently building.
 
 ### Future/Roadmap
 
 - We strive to be transparent about our [product roadmap](https://aka.ms/winui3/feature-roadmap). Great examples of feedback to help us achieve this are:
-  - "I'd like to know the roadmap through `<`timeframe`>`. Otherwise, I can't do `<`goal`>`. "
-  - "The roadmap `<`certain aspect - e.g., changes too much, not detailed enough, etc.`>`prevents me from being able to do `<`goal`>`. If you would instead `<`proposed alternative`>`, that would result in `<`clear benefit`>`."
+  - "I'd like to know the roadmap through \<timeframe\>. Otherwise, I can't do \<goal\>."
+  - "The roadmap \<certain aspect - e.g., changes too much, not detailed enough, etc.\> prevents me from being able to do \<goal\>. If you would instead \<proposed alternative\>, that would result in \<clear benefit\>."
 
 ### Ecosystem
 
 - It's helpful to be complete in explaining what another solution achieves for you and why it is important to you.
-  - Example:"I'd like WinUI 3 to work with `<`framework, language, library, technology, etc.`>`. Without this, I can't do `<`goal`>`."
+  - Example:"I'd like WinUI 3 to work with \<framework, language, library, technology, etc.\>. Without this, I can't do \<goal\>."
 
 ### Prioritization within WinUI
 
 - There is often trade-off required when adjusting priorities - please be clear in comparing what is more important vs. less important to you, and the reason why.
-  - Example: "I think `<`specific area or feature set`>` should be prioritized before `<`other specific area or feature set`>` so that I can achieve `<`goal`>`. Without this, I have to `<`alternative`>`. "  
+  - Example: "I think \<specific area or feature set\> should be prioritized before \<other specific area or feature set\> so that I can achieve \<goal\>. Without this, I have to \<alternative\>. "  
 
 ### Engagement
 
 - Engagement includes feedback about learning materials and resources. It is always helpful to know where you prefer to be engaged and how you prefer to learn.
-  - "I would like to hear more about `<`specific topic`>` in `<`resource`>` so that I can achieve `<`goal`>`."
-  - "`<`Resource`>` could be more inclusive and accessible if you considered `<`alternative`>` because `<`benefit`>`. Have you considered making these changes?"
+  - "I would like to hear more about \<specific topic\> in \<resource\> so that I can achieve \<goal\>."
+  - "\<Resource\> could be more inclusive and accessible if you considered \<alternative\> because \<benefit\>. Have you considered making these changes?"
 
    Many of the resources we provide are also open source themselves! It can sometimes be more effective to leave feedback on the more specific repo. This includes:
 
@@ -65,7 +65,7 @@ Try this:
 ### Team Process
 
 - Team process includes feedback about our repo and overall communication. Suggestions for improvement and proposed alternatives are very helpful here.
-  - Example: "`<`specific aspect of team process - e.g., response frequency, format`>` of the repo is making it hard for me to achieve `<`goal`>`. Please consider doing `<`alternative`>` instead because that would help `<`action`>`"
+  - Example: "\<specific aspect of team process - e.g., response frequency, format\> of the repo is making it hard for me to achieve \<goal\>. Please consider doing \<alternative\> instead because that would help \<action\>."
 
 ## Mutual respect
 

SECURITY.md

@@ -1,6 +1,6 @@
 <!-- BEGIN MICROSOFT SECURITY.MD V0.0.5 BLOCK -->
 
-## Security
+# Security
 
 Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
 
@@ -12,7 +12,7 @@ If you believe you have found a security vulnerability in any Microsoft-owned re
 
 Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
 
-If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).
+If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/msrc/pgp-key-msrc).
 
 You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
 
@@ -36,6 +36,6 @@ We prefer all communications to be in English.
 
 ## Policy
 
-Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/msrc/cvd).
 
 <!-- END MICROSOFT SECURITY.MD BLOCK -->

docs/contribution_workflow.md

@@ -81,7 +81,7 @@ This pipeline builds your change and runs automated tests.
 These tests should match what you're able to run with local automated testing using Test Explorer.
 It also creates a NuGet package to match your change.
 
-### license/cla
+- license/cla
 
 This check confirms that you have completed the [CLA](https://cla.microsoft.com).
 

docs/debugging_buildfailures.md

@@ -6,10 +6,12 @@ Generally, it is encouraged to collect binlog files through the CLI of MSBuild a
 
 ## Collecting binlogs through Visual Studio
 
-1. Download the VS **Project System Tools** extension: [For VS 2019](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.ProjectSystemTools) | [For VS 2022](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.ProjectSystemTools2022)
-2. Set the **Build Log File** verbosity to `Diagnostics`: Tools > Options > Projects and Solutions > MSBuild project build log file verbosity:
+1. Download the VS **Project System Tools** extension:
+   - [For VS 2019](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.ProjectSystemTools)
+   - [For VS 2022](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.ProjectSystemTools2022)
+2. Set the **Build Log File** verbosity to `Diagnostics`: **Tools** > **Options** > **Projects and Solutions** > **MSBuild project build log file verbosity**:
    ![Screenshot of Build and run options](./images/binlog-images/buildandrunoptions.png)
-3. Go to View > Other Windows > Build Logging:
+3. Go to **View** > **Other Windows** > **Build Logging**:
    ![Screenshot of Build Logging menu item](./images/binlog-images/buildlogging_menuitem.png)
 4. To start taking logs, press the play button:
 ![Screenshot of Build Logging window](./images/binlog-images/buildlogging_window.png)

docs/debugging_crashes.md

@@ -28,7 +28,7 @@ In [WinDbg](https://learn.microsoft.com/windows-hardware/drivers/debugger/debugg
 
 ### Other options
 
-Another option is to set some regkeys to tell Windows to keep some crash dumps locally (see <https://learn.microsoft.com/windows/win32/wer/collecting-user-mode-dumps>). For example, running these commands in an administrative command prompt will set regkeys to tell Windows to save full (type=2) dumps into `C:\dumps`:
+Another option is to set some regkeys to tell Windows to keep some crash dumps locally (see [Collecting User-Mode Dumps](https://learn.microsoft.com/windows/win32/wer/collecting-user-mode-dumps)). For example, running these commands in an administrative command prompt will set regkeys to tell Windows to save full (type=2) dumps into `C:\dumps`:
 
 ```cmd
     reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps" /v DumpFolder /d "C:\dumps"
@@ -39,7 +39,7 @@ After you reproduce the crash, you should find a dump in the specified folder.
 
 You can automate crash dump collection and filing bugs by following these steps:
 
-1. Download the script at <https://aka.ms/RNW/analyze-crash.ps1>, for example to `C:\temp`
+1. Download the script at [analyze-crash.ps1](https://aka.ms/RNW/analyze-crash.ps1), for example to `C:\temp`
 2. Open an admin PowerShell. If you haven't enabled running unsigned scripts yet, do that by running: `Set-ExecutionPolicy Unrestricted`
 3. Run the script and pass it the name of your app's exe: `C:\temp\analyze-crash.ps1 -ExeName MyApp -Repo microsoft/microsoft-ui-xaml`
 The script will set up automatic crash dump collection for your app, download the native debugging tools (including the command-line debugger cdb), and ask you to reproduce the crash.
@@ -57,12 +57,12 @@ But if it is a stowed exception crash, which has exception code: 0xc000027b, the
 
 Stowed exception crashes save away a possible error, which gets used later if no one handles the exception.
 XAML sometimes decides the error is fatal immediately, in which case the direct crash stack may be good, but more frequently the stack has unwound before it was determined to be fatal.
-This channel9 talk describes stowed exceptions in more detail: <https://channel9.msdn.com/Shows/Inside/C000027B?term=stowed%20exception&lang-en=true>.
+This channel9 talk describes stowed exceptions in more detail: [Channel 9 talk on stowed exceptions](https://channel9.msdn.com/Shows/Inside/C000027B?term=stowed%20exception&lang-en=true).
 
 For stowed exception crashes, you can get more info on the crash by loading a crash dump in WinDbg and then using !pde.dse to dump the stowed exceptions.
-The !pde debugger extension is available [here](https://onedrive.live.com/?authkey=%21AJeSzeiu8SQ7T4w&id=DAE128BD454CF957%217152&cid=DAE128BD454CF957) in the PDE*.zip.
+The !pde debugger extension is available [PDE debugger extension download](https://onedrive.live.com/?authkey=%21AJeSzeiu8SQ7T4w&id=DAE128BD454CF957%217152&cid=DAE128BD454CF957) in the PDE*.zip.
 (It is linked off the channel9 page above.)
-Put the appropiate x64 or x86 dll in that zip in the winext directory of a WinDbg install, and then "!pde.dse" should work on stowed exception crash dumps.
+Put the appropriate x64 or x86 dll in that zip in the winext directory of a WinDbg install, and then "!pde.dse" should work on stowed exception crash dumps.
 
 Frequently there will be multiple stowed exceptions, with some at the end which got handled/ignored.
 Most commonly, the first stowed exception is the interesting one.

docs/feature_proposal_process.md

@@ -51,7 +51,7 @@ Our contribution guidelines can be found [in this file](../CONTRIBUTING.md).
 Once a feature is complete and tested according to the [contribution guidelines](../CONTRIBUTING.md) you can send us a PR to merge it to main.
 
 8. **Documentation and sample updates**
-We will update the [documentation on learn.microsoft.com](https://learn.microsoft.com/windows/uwp) and if applicable add a sample to the [XAML Controls Gallery](https://github.com/Microsoft/Xaml-Controls-Gallery) app.
+We will update the [documentation on learn.microsoft.com](https://learn.microsoft.com/windows/uwp) and if applicable add a sample to the [WinUI 3 Gallery](https://github.com/microsoft/WinUI-Gallery) app.
 Feel free to also contribute to docs and samples!  
 Once the docs and samples are updated we'll close the issue.