From 5031da6c9e696ce62dcf0e152481851e29de003c Mon Sep 17 00:00:00 2001 From: Jeremy M Rivera Date: Wed, 20 Nov 2024 17:30:50 -0500 Subject: [PATCH] docs: grammatical/syntactical revisions in most of the docs --- doc/run-partial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/run-partial.md b/doc/run-partial.md index a523a4f057..e948734727 100644 --- a/doc/run-partial.md +++ b/doc/run-partial.md @@ -42,7 +42,7 @@ function runPartialRecursive(context, options = {}, win = window) { **important**: The order in which these methods are called matters for performance. Internally, axe-core constructs a flattened tree when `axe.utils.getFrameContexts` is called. This is fairly slow, and so should not happen more than once per frame. When `axe.runPartial` is called, that tree will be used if it still exists. Since this tree can get out of sync with the actual DOM, it is important to call `axe.runPartial` immediately after `axe.utils.getFrameContexts`. -To run efficiently, axe.runPartial calls should happen in parallel, so that, when possible, browsers can test multiple frames simultaneously. +To run efficiently, `axe.runPartial` calls should happen in parallel, so that, when possible, browsers can test multiple frames simultaneously. ## axe.finishRun(partialResults, options): Promise