Skip to content

Commit 6d84093

Browse files
docs: Rename inlang VSCode extension to Sherlock (#1032 by @felixhaeberle)
Co-authored-by: Jan Amann <[email protected]>
1 parent c523a67 commit 6d84093

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/pages/docs/workflows/vscode-integration.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ To improve the workflow for managing messages right from your code editor, you c
77
These extensions are known to support `next-intl`:
88

99
1. [i18n Ally](#i18n-ally)
10-
2. [inlang IDE extension](#inlang)
10+
2. [Sherlock](#sherlock)
1111

1212
## i18n Ally [#i18n-ally]
1313

@@ -29,7 +29,7 @@ These extensions are known to support `next-intl`:
2929
"i18n-ally.keystyle": "nested"
3030
```
3131

32-
## inlang IDE extension [#inlang]
32+
## Sherlock [#sherlock]
3333

3434
**Features:**
3535

@@ -41,7 +41,7 @@ These extensions are known to support `next-intl`:
4141

4242
**Setup:**
4343

44-
1. Install [the inlang IDE extension](https://marketplace.visualstudio.com/items?itemName=inlang.vs-code-extension)
44+
1. Install the [Sherlock VS Code extension](https://marketplace.visualstudio.com/items?itemName=inlang.vs-code-extension)
4545
2. Configure the extension in your project via `project.inlang/settings.json`:
4646

4747
```json filename="project.inlang/settings.json"
@@ -58,4 +58,4 @@ These extensions are known to support `next-intl`:
5858
}
5959
```
6060

61-
Learn more in the inlang docs: [Setting up next-intl with the IDE extension](https://inlang.com/g/hhfueysj/guide-nilsjacobsen-nextIntlIdeExtension?ref=next-intl)
61+
Learn more in the inlang docs: [Setting up next-intl with the Sherlock extension](https://inlang.com/g/hhfueysj/guide-nilsjacobsen-nextIntlIdeExtension?ref=next-intl)

0 commit comments

Comments
 (0)