From 6a0f845cfaf0795c2898781e795267f4b07a3051 Mon Sep 17 00:00:00 2001 From: Aaron Taylor Date: Sat, 4 Apr 2020 23:40:16 -0700 Subject: [PATCH 1/1] Fixed minor typos. --- stdlib/README.md | 2 +- syntax_highlighting/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/stdlib/README.md b/stdlib/README.md index 6c26770..9119b75 100644 --- a/stdlib/README.md +++ b/stdlib/README.md @@ -167,7 +167,7 @@ Be cautious when pushing constants in your code for use as bit arrays. Due to the mismatch between the VVhitespace language's sign-magnitude representation of integers and the interpreter's internal twos-complement representation, bit arrays with a leading `1` (i.e. negative numbers) may appear quite different -then expected in your source code. +than expected in your source code. For example, to push a 64-bit array of all `1`'s on to the stack we must push `SSTTN`, or `-1`. diff --git a/syntax_highlighting/README.md b/syntax_highlighting/README.md index b5eb403..b1dd1b9 100644 --- a/syntax_highlighting/README.md +++ b/syntax_highlighting/README.md @@ -77,7 +77,7 @@ Create a file named `~/.vim/syntax/vvhitespace.vim` containing the following: That's it! You should now see syntax highlighting when opening files with names ending in `*.pvvs`. -If you don't any see syntax highlighting, check your `.vimrc` and other config +If you don't see any syntax highlighting, check your `.vimrc` and other config locations for conflicting options. Try manually enabling syntax highlighting with the `syntax on` configuration directive. -- 2.20.1