From 1f4c1a17aae271dde88b23b15eca85dd727806bb Mon Sep 17 00:00:00 2001
From: joyc-bq <95259163+joyc-bq@users.noreply.github.com>
Date: Fri, 3 Jan 2025 16:00:27 -0800
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: Sophia Chu <112967780+sophia-bq@users.noreply.github.com>
---
 docs/using-the-nodejs-wrapper/UsingTheNodejsWrapper.md          | 2 +-
 .../using-plugins/UsingTheFastestResponseStrategyPlugin.md      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/using-the-nodejs-wrapper/UsingTheNodejsWrapper.md b/docs/using-the-nodejs-wrapper/UsingTheNodejsWrapper.md
index 0964bdaa..62509bc5 100644
--- a/docs/using-the-nodejs-wrapper/UsingTheNodejsWrapper.md
+++ b/docs/using-the-nodejs-wrapper/UsingTheNodejsWrapper.md
@@ -131,7 +131,7 @@ The AWS Advanced NodeJS Wrapper has several built-in plugins that are available
 | [Read Write Splitting Plugin](./using-plugins/UsingTheReadWriteSplittingPlugin.md)                            | `readWriteSplitting`      | Aurora                          | Enables read write splitting functionality where users can switch between database reader and writer instances.                                                                                                                                                                                                                                                                                                                                                                                                        | None                                                                                                                           |
 | [Aurora Initial Connection Strategy Plugin](./using-plugins/UsingTheAuroraInitialConnectionStrategyPlugin.md) | `initialConnection`       | Aurora                          | Allows users to configure their initial connection strategy to reader cluster endpoints.                                                                                                                                                                                                                                                                                                                                                                                                                               | None                                                                                                                           |
 | [Aurora Limitless Connection Plugin](./using-plugins/UsingTheAuroraInitialConnectionStrategyPlugin.md)        | `limitless`               | Aurora                          | Allows users to use Aurora Limitless Database and effectively load-balance load between available transaction routers.                                                                                                                                                                                                                                                                                                                                                                                                 | None                                                                                                                           |
-| [Fastest Response Strategy Plugin](./using-plugins/UsingTheFastestResponseStrategyPlugin.md)                  | `fastestResponseStrategy` | Aurora                          | When read-write splitting is enabled, this plugin selects the reader to switch to based on the host with the fastest response time. The plugin achieves this by periodically monitoring the hosts' response times and storing the fastest host in a cache. **Note:** the `readerHostSelector` strategy must be set to `fastestResponse` in the user-defined connection properties in order to enable this plugin. See [reader selection strategies](./ReaderSelectionStrategies.md)                                    | None                                                                                                                           |
+| [Fastest Response Strategy Plugin](./using-plugins/UsingTheFastestResponseStrategyPlugin.md)                  | `fastestResponseStrategy` | Aurora                          | When read-write splitting is enabled, this plugin selects the reader to switch to based on the host with the fastest response time. The plugin achieves this by periodically monitoring the hosts' response times and storing the fastest host in a cache.<br><br> :warning:**Note:** the `readerHostSelector` strategy must be set to `fastestResponse` in the user-defined connection properties in order to enable this plugin. See [reader selection strategies](./ReaderSelectionStrategies.md)                                    | None                                                                                                                           |
 
 In addition to the built-in plugins, you can also create custom plugins more suitable for your needs.
 For more information, see [Custom Plugins](../development-guide/LoadablePlugins.md#using-custom-plugins).
diff --git a/docs/using-the-nodejs-wrapper/using-plugins/UsingTheFastestResponseStrategyPlugin.md b/docs/using-the-nodejs-wrapper/using-plugins/UsingTheFastestResponseStrategyPlugin.md
index ba249d3a..d0d40849 100644
--- a/docs/using-the-nodejs-wrapper/using-plugins/UsingTheFastestResponseStrategyPlugin.md
+++ b/docs/using-the-nodejs-wrapper/using-plugins/UsingTheFastestResponseStrategyPlugin.md
@@ -1,6 +1,6 @@
 ## Fastest Response Strategy Plugin
 
-The Fastest Response Strategy Plugin is a host selection strategy plugin monitoring the response time of each reader host, and returns the host with the fastest response time. The plugin stores the fastest host in a cache so it can easily be retrieved again.
+The Fastest Response Strategy Plugin is a host selection strategy plugin that monitors the response time of each reader host, and returns the host with the fastest response time. The plugin stores the fastest host in a cache so it can easily be retrieved again.
 
 The host response time is measured at an interval set by `responseMeasurementIntervalMs`, at which time the old cache expires and is updated with the current fastest host.