Add EOF linebreak

Author: matkoch

topics/Architecture/Architecture_Overview.md

@@ -62,4 +62,4 @@ This is where support for Live Templates, ReSharper's snippet-based code generat
 
 ### Refactorings
 
-ReSharper's support for [Refactoring](Refactoring.md) is contained here. These assemblies contain the necessary base classes in order to create and execute your own refactoring workflows.
+ReSharper's support for [Refactoring](Refactoring.md) is contained here. These assemblies contain the necessary base classes in order to create and execute your own refactoring workflows.

topics/CustomLanguages/BuildingPsiTree.md

@@ -40,4 +40,4 @@ The parser implements the `IParser` interface, and is usually generated from a `
 
 A handwritten parser is useful if the language is extremely simple, or if the language is too complex to be represented in a `.psi` file easily. Another reason for using a handwritten parser is if the language is a superset of another language. For example, TypeScript files are a superset of JavaScript files, so can reuse parts of the parser, for statements, method definitions, etc. A hand rolled parser makes it easier to call into parts of another parser.
 
-ReSharper supports incremental re-parsing, whereby only the affected subtree is replaced, rather than having to reparse the whole file. This requires special block nodes that know how to reparse their own content.
+ReSharper supports incremental re-parsing, whereby only the affected subtree is replaced, rather than having to reparse the whole file. This requires special block nodes that know how to reparse their own content.

topics/CustomLanguages/CustomLanguages_Overview.md

@@ -281,4 +281,4 @@ protected override bool Skip(TokenNodeType tokenType)
 {
   return MyLanguageService.TokensToSkip[tokenType];
 }
-```
+```

topics/CustomLanguages/HtmlLike.md

@@ -36,4 +36,4 @@ ReSharper provides the following:
 
 * Language registration - `HtmlLanguageService` to act as a base class for the [PSI Language Service](PsiLanguageDefinition.md).
 * [Lexing](HtmlLike_Lexing.md) - `HtmlCompoundLexer` and `HtmlCompoundIncrementalLexer` which interleaves lexing the custom parts of the language with standard HTML.
-* Parsing - `IWebTreeBuilder` and the `WebTreeBuilder` base class to parse the mix of custom and traditional HTML syntax. HTML-like languages use custom written parsers rather than parsers generated with `PsiGen` and `.psi` files. This also means that the PSI element types are also generated by hand - the syntax of HTML and its derived languages is small and regular enough that this is possible.
+* Parsing - `IWebTreeBuilder` and the `WebTreeBuilder` base class to parse the mix of custom and traditional HTML syntax. HTML-like languages use custom written parsers rather than parsers generated with `PsiGen` and `.psi` files. This also means that the PSI element types are also generated by hand - the syntax of HTML and its derived languages is small and regular enough that this is possible.

topics/CustomLanguages/HtmlLike/ExtendingHtml.md

@@ -18,4 +18,4 @@ This means that HTML files are treated as "Angular HTML" files, and are now asso
 
 This does not affect compound lexers - typically, they pass in a new instance of `HtmlLexerFactory`. To get Angular support in a custom HTML-like language, pass in an instance of `Angular2HtmlLexerFactory`.
 
-In order to match ReSharper behaviour, the custom language should check to see if Angular support is enabled, by taking in an instance of the `AngularIsEnabledProvider` shell component, and comparing the `GlobalAngularLevel` to `AngularLevel.None`.
+In order to match ReSharper behaviour, the custom language should check to see if Angular support is enabled, by taking in an instance of the `AngularIsEnabledProvider` shell component, and comparing the `GlobalAngularLevel` to `AngularLevel.None`.

topics/CustomLanguages/HtmlLike/HtmlLike_Lexing.md

@@ -92,4 +92,4 @@ public short NStates { get { return (short) yy_state_dtrans.Length; } }
     <div class="@MyClass" />
     ```
 
-    This could be implemented as a `RAW_HTML` token that spans from the start of the element up to the `@` symbol - `<div class="`. The HTML lexer will then return tokens for the opening bracket, the element, the attribute name, the equals, the quote symbol and then relinquish control to the base lexer, which will return tokens for the expression - `@MyClass`. It can then return `RAW_HTML` for the closing quotes and the closing element bracket - `" />`. Because the HTML lexer state is preserved, HTML lexing will continue as expected, and the HTML tokens are correct.
+    This could be implemented as a `RAW_HTML` token that spans from the start of the element up to the `@` symbol - `<div class="`. The HTML lexer will then return tokens for the opening bracket, the element, the attribute name, the equals, the quote symbol and then relinquish control to the base lexer, which will return tokens for the expression - `@MyClass`. It can then return `RAW_HTML` for the closing quotes and the closing element bracket - `" />`. Because the HTML lexer state is preserved, HTML lexing will continue as expected, and the HTML tokens are correct.

topics/CustomLanguages/InjectedPsi.md

@@ -20,4 +20,4 @@ Alternatively, for primary PSI files you can replace these calls to `GetNonInjec
 
 ```csharp
 var file = process.SourceFile.GetNonInjectedPsiFile<CSharpLanguage>();
-```
+```

topics/CustomLanguages/Parsing/Lexing/CachingLexers.md

@@ -20,4 +20,4 @@ If the underlying lexer does not implement `IIncrementalLexer`, the `Rescan` met
 
 If a parser supports incremental parsing, it should use an instance of `CachingLexer` as its lexer - the `ToCachingLexer` extension method on `ILexer` will create this for you.
 
-More detail is provided in the section on incremental parsing.
+More detail is provided in the section on incremental parsing.

topics/CustomLanguages/Parsing/Lexing/CsLex.md

@@ -327,4 +327,4 @@ CsLex is Copyright 2000 by Brad Merrill
 
 Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both the copyright notice and this permission notice and warranty disclaimer appear in supporting documentation, and that the name of the authors or their employers not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
 
-The authors and their employers disclaim all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall the authors or their employers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of this software.
+The authors and their employers disclaim all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall the authors or their employers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of this software.

topics/CustomLanguages/Parsing/Lexing/FilteringLexers.md

@@ -86,4 +86,4 @@ When the parser builds a PSI tree, the resulting tree needs to cover the entire
 
 After parsing with a filtering lexer, a *missing token inserter* must be run to reinsert these missing tokens. The `MissingTokenInserterBase` abstract base class provides a base implementation, by walking the PSI tree and calling the `ProcessLeafElement` abstract method for each leaf element.
 
-More details can be found in the Parsers section.
+More details can be found in the Parsers section.