From 58524657fec62fbd4ad4aa90299436d791cf0604 Mon Sep 17 00:00:00 2001
From: Haley Weslin <15714156-hweslin@users.noreply.gitlab.com>
Date: Tue, 5 Sep 2023 16:05:18 +0000
Subject: [PATCH] setting not settings: struct.RoutingContext.html
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

"by settings ‘force_refresh’" needs to use the "setting" word.

After changing it, build_docs.sh fixes rustdoc for
veilid_core/struct.RoutingContext.html
---
 veilid-core/src/veilid_api/routing_context.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/veilid-core/src/veilid_api/routing_context.rs b/veilid-core/src/veilid_api/routing_context.rs
index 5b335845..6e7a9a49 100644
--- a/veilid-core/src/veilid_api/routing_context.rs
+++ b/veilid-core/src/veilid_api/routing_context.rs
@@ -284,7 +284,7 @@ impl RoutingContext {
 
     /// Gets the latest value of a subkey
     ///
-    /// May pull the latest value from the network, but by settings 'force_refresh' you can force a network data refresh
+    /// May pull the latest value from the network, but by setting 'force_refresh' you can force a network data refresh
     ///
     /// Returns `None` if the value subkey has not yet been set
     /// Returns `Some(data)` if the value subkey has valid data