devicetree-language-server 0.1.1 → 0.2.0

package/README.md

@@ -45,7 +45,7 @@ interface Settings {
 }
 ```
 
-Sample configuration in for `kakoune` with `Zephyr` 3.7.99 or lator.
+Sample configuration in for `kakoune` with `Zephyr` 3.7.99 or later.
 Contribution by [topisani](https://github.com/topisani)
 
 ```
@@ -166,7 +166,7 @@ Completions are context aware of the document state on the line the action is re
 - On node name/label reference; will list all the places where the node is altered. /delete-node/ cases are not listed.
 - On property name; will list all the places where the property is assigned a value. Note: defining a property name with no assign (empty) is equal to assigning a truthful value and hence it will also be shown.
 
-NOTE: If for example a node with name node1 has been created, then deleted, and then created again, depending on where the definition call is made in the file, in one case one will get the definition from before the delete keyword, and in the other case the definiton from under the delete keyword.
+NOTE: If for example a node with name node1 has been created, then deleted, and then created again, depending on where the definition call is made in the file, in one case one will get the definition from before the delete keyword, and in the other case the definition from under the delete keyword.
 
 ### Find Declarations
 
@@ -186,10 +186,6 @@ NOTE: The references will stop at the definition, hence, if for example a node w
 
 - On hover over the node name, a tooltip will show the final state of that node. If bindings are used it will also include the description from the binding files.
 
-### Limitations
-
-Parsing will only look at the files the devicetree uses. C header files will not be parsed to keep parsing fast enough. Hence there is no check on whether a macro exists and therefore there is no type checking.
-
 ## Bindings
 
 At the moment, this LSP only supports bindings for the Zephyr project. Feel free to contribute to this project or reach out to request other formats.
@@ -200,7 +196,7 @@ Refactoring is possible on the following elements:
 
 - Node names
 - Node labels
-- Propery names
+- Property names
 
 Given that in some cases the files included in a devicetree might come from an SDK which should not be edited, one can configure "lockRenameEdits" in the settings to lock refactoring from being permitted on any elements which would otherwise effect edits to the files listed in "lockRenameEdits".