From 73cfaee5ec2d915af0f0709d1f665ab11257f9f9 Mon Sep 17 00:00:00 2001 From: Cory LaViska Date: Tue, 22 Mar 2022 10:59:20 -0400 Subject: [PATCH] fix typo --- docs/getting-started/installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/installation.md b/docs/getting-started/installation.md index d844b780a..eb7acf042 100644 --- a/docs/getting-started/installation.md +++ b/docs/getting-started/installation.md @@ -90,7 +90,7 @@ However, if you're [cherry picking](#cherry-picking) or [bundling](#bundling) Sh The previous approach is the _easiest_ way to load Shoelace, but easy isn't always efficient. You'll incur the full size of the library even if you only use a handful of components. This is convenient for prototyping or if you're using most of the components, but it may result in longer load times in production. To improve this, you can cherry pick the components you need. -Cherry picking can be done from your local install or [directly from the CDN](https://cdn.jsdelivr.net/npm/@shoelace-style/shoelace@%VERSION%/). This will limit the number of files the browser has to download and reduce the amount of bytes being transferred. The disadvantage is that you need to load component manually. +Cherry picking can be done from your local install or [directly from the CDN](https://cdn.jsdelivr.net/npm/@shoelace-style/shoelace@%VERSION%/). This will limit the number of files the browser has to download and reduce the amount of bytes being transferred. The disadvantage is that you need to load components manually. Here's an example that loads only the button component. Again, if you're not using a module resolver, you'll need to adjust the path to point to the folder Shoelace is in.