From 2b924dc866f98b1a3731b2c8ae7dc1c7462a8b4b Mon Sep 17 00:00:00 2001
From: Trivikram Kamat <16024985+trivikr@users.noreply.github.com>
Date: Thu, 16 Jul 2020 10:15:28 -0700
Subject: [PATCH] chore: prettify *.md files missed in #1185 (#1387)

---
 packages/middleware-stack/README.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/packages/middleware-stack/README.md b/packages/middleware-stack/README.md
index ae9a3093cf6..de379a19ae3 100644
--- a/packages/middleware-stack/README.md
+++ b/packages/middleware-stack/README.md
@@ -29,7 +29,7 @@ You can add middleware to specified step with:
 
 ```javascript
 stack.add(middleware, {
-  step: "finalizeRequest"
+  step: "finalizeRequest",
 });
 ```
 
@@ -38,7 +38,7 @@ This approach works for most cases. Sometimes you want your middleware to be exe
 ```javascript
 stack.add(middleware, {
   step: "finalizeRequest",
-  priority: "high"
+  priority: "high",
 });
 ```
 
@@ -51,12 +51,12 @@ In some cases, you might want to execute your middleware before some other known
 ```javascript
 stack.add(middleware, {
   step: "finalizeRequest",
-  name: "myMiddleware"
+  name: "myMiddleware",
 });
 stack.addRelativeTo(anotherMiddleware, {
   step: "finalizeRequest",
   relation: "before", //or 'after'
-  toMiddleware: "myMiddleware"
+  toMiddleware: "myMiddleware",
 });
 ```
 
@@ -92,7 +92,7 @@ If you specify tags for middleware, you can remove multiple middleware at a time
 ```javascript
 stack.add(middleware, {
   step: "finalizeRequest",
-  tags: ["final"]
+  tags: ["final"],
 });
 stack.removeByTag("final");
 ```