[ vim ] set syntax of md files to markdown (#55)

* [ vim ] set syntax of md files to markdown

* [ lint ] fix terminology

Author: stefan-hoeck

src/Appendices/Neovim.md

@@ -370,5 +370,5 @@ is available for some other editors, so feel free to ask what's
 available for your editor of choice, for instance on the
 [Idris 2 Discord channel](https://discord.gg/UX68fDs2jc).
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Appendices/Projects.md

@@ -886,5 +886,5 @@ an Idris library or application. Finally, we learned how to include
 external libraries in an Idris project and how to use pack to help us
 keep track of these dependencies.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/DPair.md

@@ -1202,5 +1202,5 @@ contracts between values hold. These will eventually allow
 us to define pre- and post conditions for our function
 arguments and output types.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/DataTypes.md

@@ -1364,5 +1364,5 @@ already provided by the *Prelude*.
 In the [next section](Interfaces.md), we will introduce
 *interfaces*, another approach to *function overloading*.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Dependent.md

@@ -906,5 +906,5 @@ library. Likewise, `Fin` is available from `Data.Fin` from *base*.
 In the [next section](IO.md), it is time to learn how to write effectful programs
 and how to do this while still staying *pure*.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Eq.md

@@ -1094,5 +1094,5 @@ thus reducing the need to return a `Maybe` or other failure type,
 because due to the restricted input, our functions can no longer
 fail.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Folds.md

@@ -1060,5 +1060,5 @@ In the next chapter, we are taking the concept of iterating
 over container types one step further and look at
 effectful data traversals.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Functions1.md

@@ -579,5 +579,5 @@ our own data types and how to construct and deconstruct
 values of these new types. We will also learn about
 generic types and functions.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Functions2.md

@@ -3,7 +3,7 @@
 So far, we learned about the core features of the Idris
 language, which it has in common with several other
 pure, strongly typed programming languages like Haskell:
-(Higher order) Functions, algebraic data types, pattern matching,
+(Higher-order) Functions, algebraic data types, pattern matching,
 parametric polymorphism (generic types and functions), and
 ad hoc polymorphism (interfaces and constrained functions).
 
@@ -960,5 +960,5 @@ Idris' type signatures will be of paramount importance there. Whenever
 you feel lost, add one or more holes and inspect their context to decide what to
 do next.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Functor.md

@@ -1423,5 +1423,5 @@ In the [next chapter](Folds.md) we get to learn more about
 recursion, totality checking, and an interface for
 collapsing container types: `Foldable`.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/IO.md

@@ -645,7 +645,7 @@ additional namespaces to modules. For instance, in order
 to define another function called `eval`, we need to add
 it to its own namespace (note, that all definitions in a
 namespace must be indented by the same amount of
-white space):
+whitespace):
 
 ```idris
 namespace Foo
@@ -684,7 +684,7 @@ Sometimes, even *do blocks* are too noisy to express a
 combination of effectful computations. In this case, we
 can prefix the effectful parts with an exclamation mark
 (wrapping them in parentheses if they contain additional
-white space), while leaving pure expressions unmodified:
+whitespace), while leaving pure expressions unmodified:
 
 ```idris
 getHello : IO ()
@@ -1121,5 +1121,5 @@ Now, that we had a glimpse at *monads* and the *bind* operator,
 it is time to in the [next chapter](Functor.md) introduce `Monad` and some
 related interfaces for real.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Interfaces.md

@@ -817,5 +817,5 @@ at functions and their types. We will learn about named arguments,
 implicit arguments, and erased arguments as well as some
 constructors for implementing more complex functions.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Intro.md

@@ -448,3 +448,6 @@ in Idris for real. We learn how to write our own pure
 functions, how functions compose, and how we can treat
 functions just like other values and pass them around
 as arguments to other functions.
+
+<!-- vi: filetype=idris2:syntax=markdown
+-->

src/Tutorial/Predicates.md

@@ -1365,5 +1365,5 @@ arguments, which Idris should try to construct on its own if
 it has enough information about the structure of a function's
 arguments.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Prim.md

@@ -1407,5 +1407,5 @@ things perform well at runtime and compile time. I'm experimenting
 with a library, which deals with these issues. It is not yet finished,
 but you can have a look at it [here](https://github.com/stefan-hoeck/idris2-prim).
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->

src/Tutorial/Traverse.md

@@ -1144,5 +1144,5 @@ There's one still missing - `Alternative` - but this will
 have to wait a bit longer, because we need to first make
 our brains smoke with some more type-level wizardry.
 
-<!-- vi: filetype=idris2
+<!-- vi: filetype=idris2:syntax=markdown
 -->