From 4f055b9abc2a674689c6722898003c48e0b6625b Mon Sep 17 00:00:00 2001 From: Max Schmitt Date: Tue, 24 Oct 2017 23:44:43 +0200 Subject: [PATCH] Fixed typos (#36804) `to sigmal a function references` => `to signal a function reference` `Alternative is to...` => `An alternative is to...` --- extensions/typescript/syntaxes/Readme.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/extensions/typescript/syntaxes/Readme.md b/extensions/typescript/syntaxes/Readme.md index d45fc854245..3e1cf32a0e2 100644 --- a/extensions/typescript/syntaxes/Readme.md +++ b/extensions/typescript/syntaxes/Readme.md @@ -7,10 +7,10 @@ To update to the latest version: Migration notes and todos: - differentiate variable and function declarations from references - - I suggest we use a new scope segment 'function-call' to sigmal a function references, and 'definition' to the declaration. Alternative is to use 'support.function' everywhere. + - I suggest we use a new scope segment 'function-call' to signal a function reference, and 'definition' to the declaration. An alternative is to use 'support.function' everywhere. - I suggest we use a new scope segment 'definition' to the variable declarations. Haven't yet found a scope for references that other grammars use. - rename scope to return.type to return-type, which is already used in other grammars - rename entity.name.class to entity.name.type.class which is used in all other grammars I've seen -- do we really want to have the list of all the 'library' types (Math, Dom...). It adds a lot of size to the grammar, lots of special rules and is not really correct as it depends on the JavaScript runtime which types are present. \ No newline at end of file +- do we really want to have the list of all the 'library' types (Math, Dom...). It adds a lot of size to the grammar, lots of special rules and is not really correct as it depends on the JavaScript runtime which types are present. -- GitLab