Tweak troubleshooting imstructions in README

lostintangent · lostintangent · commit ac4bbd1152d7 · 2025-06-16T10:33:25.000-07:00
diff --git a/README.md b/README.md
@@ -150,4 +150,4 @@ The `gistpad-mcp` CLI accepts the following optional flags:
 
 ## 🧰 Troubleshooting
 
-- <u>Not seeing a gist in your list?</u> Rhe GistPad MCP server caches your gist list during the lifetime of its server process (for performance reasons), and so if you add/edit/delete a gist externally, you may need to tell GistPad MCP to refresh itself. You can do this by triggering the `refresh_gists` tool.
+- <u>Not seeing a gist in your list?</u> Rhe GistPad MCP server caches your gist list during the lifetime of its server process (for performance reasons), and so if you add/edit/delete a gist externally, you may need to tell GistPad MCP to refresh itself. You can do this by triggering the `refresh_gists` tool (e.g. running `#refresh_gists` in VS Code Copilot chat).

Original file line number	Diff line number	Diff line change
@@ -150,4 +150,4 @@ The `gistpad-mcp` CLI accepts the following optional flags:
`150`	`150`
`151`	`151`	`## 🧰 Troubleshooting`
`152`	`152`
`153`		-- <u>Not seeing a gist in your list?</u> Rhe GistPad MCP server caches your gist list during the lifetime of its server process (for performance reasons), and so if you add/edit/delete a gist externally, you may need to tell GistPad MCP to refresh itself. You can do this by triggering the `refresh_gists` tool.
	`153`	+- <u>Not seeing a gist in your list?</u> Rhe GistPad MCP server caches your gist list during the lifetime of its server process (for performance reasons), and so if you add/edit/delete a gist externally, you may need to tell GistPad MCP to refresh itself. You can do this by triggering the `refresh_gists` tool (e.g. running `#refresh_gists` in VS Code Copilot chat).