Skip to content

Commit fa3f3fd

Browse files
committed
Merge pull request processing-js#28 from acusti/patch-1
wow, way to not notice this pull request. Go us. Thanks for the fix!
2 parents 17f395f + 8b86292 commit fa3f3fd

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ Some web browsers (e.g., Chrome) require secondary files to be loaded from a
107107
web server for security reasons. This means loading a web page that references
108108
a Processing.js sketch in a file via a file:/// URL vs. http:// will fail. You
109109
are particularly likely to run into this problem when you try to view your
110-
webpage directly from file, as this makes all relatively links file:/// links.
110+
webpage directly from file, as this makes all relative links file:/// links.
111111

112112
There are several ways to get around this problem. You can use a browser which
113113
does allow file:/// access, although most current browsers either have, or plan
@@ -128,10 +128,10 @@ you turn it back on. While "easy", this is unsafe.
128128
Learn More About Processing.js
129129
-------------------------------
130130
Processing developers should start with the Processing.js Quick Start Guide for
131-
Processing Developers at http://processingjs.org/reference/articles/p5QuickStart.
131+
Processing Developers at http://processingjs.org/articles/p5QuickStart.html
132132

133133
JavaScript developers should start with the Processing.js Quick Start Guide for
134-
JavaScript Developers at http://processingjs.org/reference/articles/jsQuickStart
134+
JavaScript Developers at http://processingjs.org/articles/jsQuickStart.html
135135

136136
A more detailed guide is http://processingjs.org/articles/PomaxGuide.html
137137

0 commit comments

Comments
 (0)