From 0da328e6eb623a9f3ff1772a614392a851c18e78 Mon Sep 17 00:00:00 2001
From: JGibson2019 <jacqueline.gibson@microsoft.com>
Date: Tue, 12 Dec 2023 16:26:56 -0800
Subject: [PATCH] fix: Change "Usage" heading in README to all caps (#1180)

#### Details
This is updating the text in the README for the Usage section to now
show "USAGE".
<!-- Usually a sentence or two describing what the PR changes -->

##### Motivation
Triggering a build to confirm that the new GH token is being consumed
properly
<!-- This can be as simple as "addresses issue #123" -->

##### Context
Quarterly DRI rotation
<!-- Are there any parts that you've intentionally left out-of-scope for
a later PR to handle? -->

<!-- Were there any alternative approaches you considered? What
tradeoffs did you consider? -->

#### Pull request checklist
<!-- If a checklist item is not applicable to this change, write "n/a"
in the checkbox -->
- [ ] PR title respects [Conventional
Commits](https://www.conventionalcommits.org) (starts with `fix:`,
`feat:`, etc, and is suitable for user-facing release notes)
- [ ] PR contains no breaking changes, **OR** description of both PR
**and final merge commit** starts with `BREAKING CHANGE:`
- [ ] (if applicable) Addresses issue: #0000
- [ ] Added relevant unit tests for your changes
- [ ] Ran `yarn precheckin`
- [ ] Verified code coverage for the changes made
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 2d1d95d1..f2543e42 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,7 @@ Convert [axe-core](https://github.com/dequelabs/axe-core) accessibility scan res
 
 Use this with the [Sarif Viewer Build Tab Azure DevOps Extension](https://marketplace.visualstudio.com/items?itemName=sariftools.sarif-viewer-build-tab) to visualize accessibility scan results in the build results of an [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) build.
 
-## Usage
+## USAGE
 
 Before using axe-sarif-converter, you will need to run an [axe](https://github.com/dequelabs/axe-core) accessibility scan to produce some axe results to convert. Typically, you would do this by using an axe integration library for your favorite browser automation tool ([@axe-core/puppeteer](https://github.com/dequelabs/axe-core-npm/tree/develop/packages/puppeteer), [@axe-core/webdriverjs](https://github.com/dequelabs/axe-core-npm/tree/develop/packages/webdriverjs), [cypress-axe](https://github.com/avanslaars/cypress-axe)).