From c87f324375dfbf961902dab08d34973f6fb5a3f1 Mon Sep 17 00:00:00 2001 From: Junwei Zhao Date: Sun, 5 Apr 2020 05:47:56 +1000 Subject: [PATCH] update settings --- categories/go.md | 2 +- categories/iot.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/categories/go.md b/categories/go.md index f488e27..4a9b1a3 100644 --- a/categories/go.md +++ b/categories/go.md @@ -149,7 +149,7 @@ func main() { ### RWMutex !> A RWMutex is a reader/writer mutual exclusion lock. The lock can be held by an arbitrary number of readers or a single writer. The zero value for a RWMutex is an unlocked mutex. -!> In other words, readers don't have to wait for each other. They only have to wait for writers holding the lock. +In other words, readers don't have to wait for each other. They only have to wait for writers holding the lock. ### string literals diff --git a/categories/iot.md b/categories/iot.md index d14c569..b407944 100644 --- a/categories/iot.md +++ b/categories/iot.md @@ -23,7 +23,7 @@ The most important aspect of pub/sub is the decoupling of the publisher of the m * **Synchronization decoupling**: Operations on both components do not need to be interrupted during publishing or receiving. -> In summary, the pub/sub model removes direct communication between the publisher of the message and the recipient/subscriber. The filtering activity of the broker makes it possible to control which client/subscriber receives which message. The decoupling has three dimensions: space, time, and synchronization. +!> In summary, the pub/sub model removes direct communication between the publisher of the message and the recipient/subscriber. The filtering activity of the broker makes it possible to control which client/subscriber receives which message. The decoupling has three dimensions: space, time, and synchronization. MQTT embodies all the aspects of pub/sub that we’ve mentioned: