Skip to content

Commit 93342ee

Browse files
committed
fix confusing wording in caching docs
1 parent 7b88797 commit 93342ee

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/caching.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,11 +72,13 @@ request to the tito API and return the results. It will also cache the results
7272
in the `cache` (which is the SQLite cache). The next time you call
7373
`getScheduledEvents` it will return the cached value if the cached value is less
7474
than 30 days old. If the cached value is older than 24 hours, it will also make
75-
a request to the tito API in the. If the cache value is more than 30 days old,
76-
it will wait until the tito request is complete and then return the fresh value.
75+
a request to the tito API. If the cache value is more than 30 days old, it will
76+
wait until the tito request is complete and then return the fresh value.
7777

7878
Bottom line: You make the request much less often and users are never waiting
79-
for it.
79+
for it. Every situation will require you think through the implications of
80+
caching and acceptable stale-ness, but the point is you have those levers to
81+
pull.
8082

8183
A lot more needs to be said on this subject (an entire workshop full!), but this
8284
should be enough to get you going!

0 commit comments

Comments
 (0)