From 32d11d1b3b8872c94a95a4dc19c88e050be85bf0 Mon Sep 17 00:00:00 2001 From: Matt Richardson Date: Thu, 27 Oct 2016 15:36:29 -0400 Subject: [PATCH] Add'l readability edits --- appendix/01/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appendix/01/README.md b/appendix/01/README.md index 9ced2ee..bbedbaf 100644 --- a/appendix/01/README.md +++ b/appendix/01/README.md @@ -1,6 +1,6 @@ ## How to run the examples on a Raspberry Pi? -A few years ago, assuming that everybody have a computer with a GPU was a long shot. Now, most computers have a graphical processing unit, but is a high bar for a requirement in a workshop or class for example. +A few years ago, assuming that everybody has a computer with a GPU was a long shot. Now, most computers have a graphical processing unit, but is a high bar for a requirement in a workshop or class, for example. Thanks to the [Raspberry Pi Foundation](http://www.raspberrypi.org/) a new type of small and cheap generation of computers (around $35 each) has found its way into classrooms. More importantly for the purposes of this book, the [Raspberry Pi](http://www.raspberrypi.org/) comes with a decent Broadcom GPU that can be accessed directly from the console. I made a [flexible GLSL live coding tool call **glslViewer**](https://github.com/patriciogonzalezvivo/glslViewer) that runs all the examples in this book. This program also has the ability to update automatically when the user saves a change to their code. What does this mean? You can edit the shader and every time you save it, the shader will be re-compile and render for you.