additions

Author: Jay-o-Way

SECURITY.md

@@ -14,17 +14,17 @@ Instead, please report them to the Microsoft Security Response Center (MSRC) at
 
 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).
 
-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). 
+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).
 
 Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
 
-  - Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
-  - Full paths of source file(s) related to the manifestation of the issue
-  - The location of the affected source code (tag/branch/commit or direct URL)
-  - Any special configuration required to reproduce the issue
-  - Step-by-step instructions to reproduce the issue
-  - Proof-of-concept or exploit code (if possible)
-  - Impact of the issue, including how an attacker might exploit the issue
+- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+- Full paths of source file(s) related to the manifestation of the issue
+- The location of the affected source code (tag/branch/commit or direct URL)
+- Any special configuration required to reproduce the issue
+- Step-by-step instructions to reproduce the issue
+- Proof-of-concept or exploit code (if possible)
+- Impact of the issue, including how an attacker might exploit the issue
 
 This information will help us triage your report more quickly.
 

docs/debugging_buildfailures.md

@@ -1,19 +1,18 @@
 # Capturing binlogs
+
 Capturing and providing binlog files can help with debugging build and packaging issues. In order to collect binlogs, please follow these steps:
 
 Generally, it is encouraged to collect binlog files through the CLI of MSBuild as they tend to be easier to diagnose, but both methods of creating binlog files are fine.
 
 ## 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)
-3. Set the **Build Log File** verbosity to `Diagnostics`: `Tools->Options->Projects and Solutions->MSBuild project build log file verbosity`:<br/>
-![Screenshot of Build and run options](./images/binlog-images/buildandrunoptions.png)
-
-3. Go to View->Other Windows->Build Logging:<br/>
-![Screenshot of Build Logging menu item](./images/binlog-images/buildlogging_menuitem.png)
 
-4. To start taking logs, press the play button:<br/>
+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:
+   ![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)
-
 5. Run the steps that resulted in errors, e.g. building your project. The steps that failed show up as "Failed". Those files have the file extension ".binlog" and can be shared to help debugging build and packaging issues.
 
 ## Collection binlogs through the command line
@@ -22,10 +21,14 @@ To collect binlogs through the command line interface of MSBuild using the Visua
 
 For example, to build your solution in x86 release and collect binlogs, you can use the following:
 
-`msbuild /p:Platform=x86 /p:Configuration=Release /bl`
+```cli
+msbuild /p:Platform=x86 /p:Configuration=Release /bl
+```
 
 If you encounter issues while creating app packages, you can use the following command to simulate collect binlogs:
 
-`msbuild /p:AppxBundlePlatforms=x86 /p:Platform=x86 /p:Configuration=Release /p:BuildAppxUploadPackageForUap=true /bl`
+```cli
+msbuild /p:AppxBundlePlatforms=x86 /p:Platform=x86 /p:Configuration=Release /p:BuildAppxUploadPackageForUap=true /bl
+```
 
 In case of investigating build failures with the WinUI source code, please run the `devcmd.cmd` script at the root of the repository first.