Skip to content

Commit 7587dca

Browse files
authored
Fix typos and enhance clarity in AGentleIntroduction.md
Corrected typos and improved clarity in the documentation.
1 parent 9e00f71 commit 7587dca

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

docs/AGentleIntroduction.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ As we know from the [Fallacies Of Distributed Computing](https://en.wikipedia.or
110110

111111
Without some extra care what can happen is that data would not be saved in the distributed cache or other nodes may not be notified of changes: this would result in out-of-sync issues.
112112

113-
wouldn't it be nice if FusionCache would help us is some way when transient error happens?
113+
Wouldn't it be nice if FusionCache would help us is some way when transient error happens?
114114

115115
Enter **Auto-Recovery**: everything is done automatically, and it just works.
116116

@@ -121,9 +121,9 @@ Read more [**here**](AutoRecovery.md).
121121

122122
Tagging is an incredibly powerful feature: cache entries can be tagged with one or more tags, and later they can be evicted all at once by just calling `RemoveByTag("my-tag")`.
123123

124-
The overall [design](https://github.com/ZiggyCreatures/FusionCache/issues/319) used to achieve this is such that, even when working against a massive cache with millions of entries, will not incur in any upfront cost (yes, even a distributed L2 like a Redis gigantic instance).
124+
The overall [design](https://github.com/ZiggyCreatures/FusionCache/issues/319) used to achieve this is such that, even when working against a massive cache with millions of entries, will not incur in any upfront cost (yes, even with a gigantic distributed cache as L2, like a big Redis instance).
125125

126-
Tagging works in any supported scenario: with or without an optional L2 (distributed level), an optional backplane, shared caches, cache key prefix, fail-safe, soft/hard timeouts, auto-recovery and everything else.
126+
Tagging works in any supported scenario: with only L1, with L1+L2, with or without an optional backplane, shared caches (both L1 and L2), cache key prefix, fail-safe, soft/hard timeouts, auto-recovery and everything else.
127127

128128
Read more [**here**](Tagging.md).
129129

@@ -132,7 +132,9 @@ Read more [**here**](Tagging.md).
132132

133133
Thanks to the design used for the Tagging feature (see above), FusionCache also supports a proper `Clear()` mechanism for the entire cache.
134134

135-
Yes, yes: the abiltiy to clear seems like an easy one but when we consider things like shared caches, cache key prefix and all the other features... it's definitely not an easy feat. But yeah, it just works.
135+
Yes, yes: the abiltiy to clear the cache seems like an easy one, but when we consider things like multiple levels, shared caches, cache key prefix and all the other features... it's definitely not an easy feat.
136+
137+
But yeah, long story short: it just works.
136138

137139
Read more [**here**](Clear.md).
138140

0 commit comments

Comments
 (0)