From db64f21beb7489f2e21b3a32c4f83eb2529c234b Mon Sep 17 00:00:00 2001 From: Kim Gardner Date: Tue, 20 Mar 2018 16:09:33 -0400 Subject: [PATCH] Typo --- docs/source/04-06-slots-and-plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/04-06-slots-and-plugins.md b/docs/source/04-06-slots-and-plugins.md index 86e3addeb..907c85862 100644 --- a/docs/source/04-06-slots-and-plugins.md +++ b/docs/source/04-06-slots-and-plugins.md @@ -120,7 +120,7 @@ The slots that are able to add functionality to comments start with `comment`, l Typically, you will manage plugins via your `plugins.json` file. If you want to remove a plugin, you would simply delete it there. However, we can also do this directly with the `plugins_config`. -Let's look at our example article, `views/article.ejs`. Here we see can we have the Talk embed, and within the embed, we can also send a configuration object. To disable a plugin visually, we can pass `true` to the property `disable_components`. Like so: +Let's look at our example article, `views/article.ejs`. Here we see we have the Talk embed, and within the embed, we can also send a configuration object. To disable a plugin visually, we can pass `true` to the property `disable_components`. Like so: ```js