From f4cf0431acc75d1e136f2180ede8415de6992fe2 Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Wed, 24 Aug 2022 14:47:29 +0100 Subject: [PATCH] Removed key emoji --- docs/pages/docs/core-concepts/remote-caching.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/docs/core-concepts/remote-caching.mdx b/docs/pages/docs/core-concepts/remote-caching.mdx index c6e842a1553ee..86f3995027b38 100644 --- a/docs/pages/docs/core-concepts/remote-caching.mdx +++ b/docs/pages/docs/core-concepts/remote-caching.mdx @@ -8,7 +8,7 @@ import Callout from "../../../components/Callout"; # Remote Caching -A major key 🔑 to Turborepo's speed is that it is both lazy and efficient—it does the least amount of work possible and it tries to never redo work that's already been done before. +A major key to Turborepo's speed is that it is both lazy and efficient—it does the least amount of work possible and it tries to never redo work that's already been done before. By default, Turborepo caches the outputs of your tasks on your machine's local file system. We call this "single-player mode." But what if you could take advantage of the computational work done by your teammates or your CI by sharing a single cache across machines? In other words, what if you could turn on "co-op multiplayer mode", or a "Dropbox" for your Turborepo cache?