Merge pull request #1173 from kianmeng/fix-typos

Fix typos

SPAWNFEST.md

@@ -20,14 +20,14 @@ The [Debug Adapter Protocol](https://microsoft.github.io/debug-adapter-protocol/
 
 ## Rationale
 
-One of the strengths of the Erlang programming language is the ability to seemlessly _debug_ and _trace_ Erlang code. Many tools and libraries exist, but they are sometimes under-utilized by the Community, either because their API is not intuitive (think to the [dbg](https://erlang.org/doc/man/dbg.html) Erlang module), or because they offer a limited, obsolete, UI (think the [debugger](http://erlang.org/doc/apps/debugger/debugger_chapter.html) application).
+One of the strengths of the Erlang programming language is the ability to seamlessly _debug_ and _trace_ Erlang code. Many tools and libraries exist, but they are sometimes under-utilized by the Community, either because their API is not intuitive (think to the [dbg](https://erlang.org/doc/man/dbg.html) Erlang module), or because they offer a limited, obsolete, UI (think the [debugger](http://erlang.org/doc/apps/debugger/debugger_chapter.html) application).
 
 We want to solve this problem by leveraging some of the existing debugging and tracing facilities provided by Erlang/OTP and bringing the debugging experience directly in the text-editor, next to the code, improving the user experience when using such
 tools.
 
 [This video](https://www.youtube.com/watch?v=ydcrdwQKqI8&t=3s) shows what debugging Erlang code is like via the _debugger_ application. [This other video](https://www.youtube.com/watch?v=ydcrdwQKqI8) shows what the same experience looks like from Emacs.
 
-Due to the editor-agnostic nature of the _DAP_ protocol, a very similar experience is delivered to users of a different developement tool, be it _Vim_, _VS Code_ or _Sublime Text 3_.
+Due to the editor-agnostic nature of the _DAP_ protocol, a very similar experience is delivered to users of a different development tool, be it _Vim_, _VS Code_ or _Sublime Text 3_.
 
 ## Project Goal
 

apps/els_core/include/els_core.hrl

@@ -207,7 +207,7 @@
                                           }.
 
 %%------------------------------------------------------------------------------
-%% Document Fiter
+%% Document Filter
 %%------------------------------------------------------------------------------
 -type document_filter() :: #{ language => binary()
                             , scheme   => binary()

apps/els_dap/src/els_dap_general_provider.erl

@@ -1,7 +1,7 @@
 %%==============================================================================
 %% @doc Erlang DAP General Provider
 %%
-%% Implements the logic for hanlding all of the commands in the protocol.
+%% Implements the logic for handling all of the commands in the protocol.
 %%
 %% The functionality in this module will eventually be broken into several
 %% different providers.

apps/els_dap/test/els_dap_general_provider_SUITE.erl

@@ -291,7 +291,7 @@ frame_variables(Config) ->
 
 -spec navigation_and_frames(config()) -> ok.
 navigation_and_frames(Config) ->
-  %% test next, stepIn, continue and check aginst expeted stack frames
+  %% test next, stepIn, continue and check against expected stack frames
   Provider = ?config(provider, Config),
   #{<<"threads">> := [#{<<"id">> := ThreadId}]} =
     els_provider:handle_request( Provider

apps/els_lsp/src/els_code_navigation.erl

@@ -36,7 +36,7 @@ goto_definition( Uri
     [] -> {error, not_in_function_clause};
     FunRanges ->
       FunRange = lists:last(FunRanges),
-      %% Find the first occurance of the variable in the function clause
+      %% Find the first occurrence of the variable in the function clause
       [POI|_] = [P || P = #{range := Range, id := Id} <- VarPOIs,
                       els_range:compare(Range, VarRange),
                       els_range:compare(FunRange, Range),
@@ -61,7 +61,7 @@ goto_definition( Uri
                       Kind =:= implicit_fun;
                       Kind =:= export_entry ->
   %% try to find local function first
-  %% fall back to bif search if unsuccesful
+  %% fall back to bif search if unsuccessful
   case find(Uri, function, {F, A}) of
     {error, Error} ->
       case is_imported_bif(Uri, F, A) of

apps/els_lsp/src/els_erlfmt_ast.erl

@@ -321,7 +321,7 @@ erlfmt_to_st(Node) ->
             %% clauses of case/if/receive/try
             erlfmt_clause_to_st(Clause);
         %% Lists are represented as a `list` node instead of a chain of `cons`
-        %% and `nil` nodes, similar to the `tuple` node. The last elemenent of
+        %% and `nil` nodes, similar to the `tuple` node. The last element of
         %% the list can be a `cons` node representing explicit consing syntax.
         {list, Pos, Elements} ->
             %% a "cons" node here means 'H | T' in isolation

specs/runtime_node.md

@@ -46,7 +46,7 @@ Initially we envisage ones for
   - "plain" project, i.e. just some random .erl files on the filesystem
     somewhere
 
-Becase the protocol between the `Server` and the `Runtime Node` will be
+Because the protocol between the `Server` and the `Runtime Node` will be
 standardised, and we will have out of the box implementations for popular
 project build systems, it becomes easy for particular Erlang production sites to
 adapt these nodes for use in their particular environments.  This includes the
@@ -77,7 +77,7 @@ The `Runtime Node` should be able to respond to the following requests.
 - provide xref information for a file
 - run dialyzer
 
-### Current Unkowns / Questions
+### Current Unknowns / Questions
 
 - Should the `Server` and `Runtime Node` share a file system? i.e. should a URI
   be usable directly in any context for the current state of a file.