updated the H1 tags to H2

Author: dcaiced0

design/ux-patterns/branding.md

@@ -10,7 +10,7 @@ Provide users with feedback as they interact with your plugin, this can be alert
 ----------
  <br />
 
-# Onboarding and branding
+## Onboarding and branding
 
 When the user is interacting with the plugin for the first time for example in the onboarding or login screen, including the plugin logo will help the user identify the plugin in the future. 
 
@@ -20,7 +20,7 @@ When the user is interacting with the plugin for the first time for example in t
 
  <br />
 
-# Customized plugin UI
+## Customized plugin UI
 
 Customizing the UI to include brand colors, will help users distinguish your plugin from native UI in XD. 
 

design/ux-patterns/index.md

@@ -13,17 +13,17 @@ UX Patterns will include UX requirements and/or UX best practices these will ens
 
  <br />
 
-# Documentation
+## Documentation
 
-### Specs and UX Requirements
+#### Specs and UX Requirements
 
-Requirements highlights key XD patterns all plugins need to follow to get approved by Adobe. 
+Requirements highlight key XD patterns all plugins need to follow to get approved by Adobe. 
 
 ![Example of specs and UX requirements](../ux-images/UX-Patterns-1-Specs.png)
 
-### Best practices
+#### Best practices
 
-Best practices provides recommendations on plugin usability and behavior, user feedback, privacy and interface guidelines. 
+Best practices provide recommendations on plugin usability and behavior, user feedback, privacy, and interface guidelines. 
 
 ![Example of a UX best practice](../ux-images/UX-Patterns-2-Best-Practices.png)
 

design/ux-patterns/messaging.md

@@ -17,7 +17,7 @@ Provide users with feedback as they interact with your plugin, this can be alert
 ----------
  <br />
 
-# Examples
+## Examples
 
 ![Operation failed to complete](../ux-images/Error-alert-example.png)
 
@@ -41,14 +41,14 @@ Information dialog - if the plugin is unable to connect to the internet to compl
 
  <br />
 
-# Alerts
+## Alerts
 
 **Use case**  
 Use alert messaging whenever the plugin cannot perform the intended task, dialogs are persistent until dismissed
 
 ![Aler dialog requirements](../ux-images/Alert-Requirements.png)
 
-### UX Requirements
+#### UX Requirements
 
 **Header**  
 Have a clear header that describes the error
@@ -61,13 +61,13 @@ Include at least one modal dismissal button to allow the user to dismiss/close t
 
 ![Alert Dialog Best Practices](../ux-images/Alert-Recommendations.png)
 
-### Best practices
+#### Best practices
 
 **Warning icon**  
 To help communicate critical information for an error you can include a warning icon next to the header
 
 **Help**  
-If a plugin has a help page, consider adding it on the error modal dialog.
+If a plugin has a help page, consider adding it to the error modal dialog.
 
 **Visual/tutorials**  
 Provide image/GIF example as part of the dialog, to help users understand the actionable solution
@@ -77,14 +77,14 @@ In the alert messages use language that is easy to understand for the user.
 
  <br />
 
-# Success
+## Success
 
 **Use case**  
 Use success messaging whenever the plugin successfully completes a task and has no visual output on the canvas.
 
 ![Alert Success Dialog example](../ux-images/Alert-Requirements.png)
 
-### UX Requirements
+#### UX Requirements
 
 **Header**  
 Have a clear header for the dialog.
@@ -97,14 +97,14 @@ Include at least one modal dismissal button to allow the user to dismiss/close t
 
  <br />
 
-# Output
+## Output
 
 **Use case**  
 If a plugin generates output that the user needs to complete a workflow, then the plugin needs to provide that information to the user.
 
 ![Plugin output example](../ux-images/Plugin-output.png)
 
-### UX Requirements
+#### UX Requirements
 
 **Plugin output**  
 In use cases like these, the plugin output can be shown in the UI, copied onto the clipboard, populated on the document or generate a file.
@@ -117,14 +117,14 @@ Require users to go into the developer console to complete an action.
 
  <br />
 
-# Permission dialogs
+## Permission dialogs
 
 **Use case**  
 Use permission dialogs when being destructive or making modifications.
 
 ![Permission dialog example](../ux-images/Permission-dialog-example.png)
 
-### UX Requirements
+#### UX Requirements
 
 **Header**   
 Have a clear header for the dialog.
@@ -140,17 +140,17 @@ Esc key or Enter key Dismisses the dialog when the “Cancel” button is in foc
 
  <br />
 
-# Loaders and Progress bars
+## Loaders and Progress bars
 Let the user know when something is happening in the background in the plugin UI. 
 
-### Determinate
+#### Determinate
 **Use case**  
 Use case If the progress can be reflected on a loader. 
 
 ![Determinate example](../ux-images/Determinate-loader-example.png)
 
 
-### Indeterminate
+#### Indeterminate
 **Use case**  
 If the progress can’t be determined then provide a loader to let the user know something is loading.
 

design/ux-patterns/modal-ux.md

@@ -12,13 +12,13 @@ This section will have recommendations when using a Modal Dialog -  Blocking UI.
 
  <br />
 
-# Specs and UX Requirements
+## Specs and UX Requirements
 
-## MacOS example
+### MacOS example
 
 ![Modal Specs](../ux-images/Modal-UX-2-Specs.png)
 
-## Specs
+### Specs
 
 **Padding**  
 The modal will have padding built-in (ex: MacOS modal will have a 40px padding). Additional padding shouldn’t be added.
@@ -27,7 +27,7 @@ The modal will have padding built-in (ex: MacOS modal will have a 40px padding).
 This is what the user can interact with before executing the plugin action. 
 
 
-## UX Requirements
+### UX Requirements
 
 **Header**  
 Have a clear header for the dialog. e.g. “name of plugin”, “description of workflow”
@@ -37,32 +37,32 @@ Have a clear header for the dialog. e.g. “name of plugin”, “description of
 Include a modal dismissal button to allow the user to cancel/close the modal and a call to action button (blue) to highlight the primary action. 
 
 
-## Best Practices
+### Best Practices
 
 **Plugin Icon**.  
 You can include a plugin icon to let the user know they are interacting with your plugin in the modal dialog
 
  <br />
 
-# Modal Dialog UI
+## Modal Dialog UI
 
-## Modal dialog plugin UI
+### Modal dialog plugin UI
 
 ![Modal Dialog](../ux-images/Modal-UX-3-Modal-Dialog.png)
 
-## Step process three buttons
+### Step process three buttons
 
 ![Step Process](../ux-images/Modal-UX-4-Step-Process.png)
 
-## Step process loader
+### Step process loader
 
 ![Loader](../ux-images/Modal-UX-5-Loader.png)
 
  <br />
 
 # Dialog buttons and key commands
 
-## Buttons
+### Buttons
 
 ![Buttons](../ux-images/Modal-UX-6-Buttons.png)
 
@@ -79,7 +79,7 @@ The secondary button is for low emphasis. It is meant to be paired with other bu
 **Negative**  
 The negative button is for high emphasis on negative or destructive actions. It should be used sparingly. It can be displayed either in standard style (visible stroke) or in quiet style.
 
-## Best practice
+### Best practice
 
 **Button Group Overflow**  
 When horizontal space is limited, button groups stack vertically. 
@@ -89,13 +89,13 @@ at the bottom.
 **Use 2 button styles maximum**  
 The top-level action within a button group should be a call to action, primary, or negative button. The subsequent buttons should always be secondary buttons of the same style (standard or quiet). Don’t combine more than 2 button styles in a button group.
 
-## Button labels
+### Button labels
 
 Button labels should be clear about the intention of the action. Button text should be 1 to 2 words and consider the number of characters.
 
 ![Button labels](../ux-images/Modal-UX-7-Button-Labels.png)
 
-## Key Commands
+### Key Commands
 
 **Esc key**  
 Dismisses the dialog. This is equivalent to choosing “Cancel”.

reference/uxp/class/WebSocket.md

@@ -70,5 +70,5 @@ Closes the websocket connection
 | Param | Type | Default | Description |
 | --- | --- | --- | --- |
 | [code] | `integer` | <code>1000</code> | A integer value as per https://developer.mozilla.org/en-US/docs/Web/API/WebSocket#close(). |
-| [reason] | `string` | <code>&quot;&quot;</code> | A human-readable string explaining why the connection is closing. Throws an exception of Error Object if invalid code or reason is passed Refer https://wiki.corp.adobe.com/pages/viewpage.action?pageId=1455687313#FileandNetworkI/OTestCases-CloseMethodbehaviorforWebSockets |
+| [reason] | `string` | <code>&quot;&quot;</code> | A human-readable string explaining why the connection is closing. Throws an exception of Error Object if invalid code or reason is passed |