From 818a4ea27225a4176fb191bed5eb329c807045a7 Mon Sep 17 00:00:00 2001 From: Kirill Bulatov Date: Sat, 22 Feb 2020 14:35:48 +0300 Subject: [PATCH] Fix a typo --- docs/user/features.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/features.md b/docs/user/features.md index e0735dcd87..a9cff34d22 100644 --- a/docs/user/features.md +++ b/docs/user/features.md @@ -177,7 +177,7 @@ Two types of inlay hints are displayed currently: In VS Code, the following settings can be used to configure the inlay hints: * `rust-analyzer.displayInlayHints` — toggles inlay hints display on or off -* `rust-analyzer.maxInlayHintLength` — shortens the hints if their length exceeds the value specified. If no value is specified (`null`), no shorteninng is applied. +* `rust-analyzer.maxInlayHintLength` — shortens the hints if their length exceeds the value specified. If no value is specified (`null`), no shortening is applied. **Note:** VS Code does not have native support for inlay hints [yet](https://github.com/microsoft/vscode/issues/16221) and the hints are implemented using decorations. This approach has limitations: the caret movement near the end of the hint may look [weird](https://github.com/rust-analyzer/rust-analyzer/issues/1623).