Update README.md

monkstone · web-flow · commit a2e9ade3afb9 · 2016-09-26T07:44:23.000+01:00
diff --git a/external_library/java/queasycam/README.md b/external_library/java/queasycam/README.md
@@ -1,3 +1,3 @@
 ### READ ME ###
 
-It is an unfortunate fact that queasycam uses `processing.core.PVector` under the hood, this does not play too well with JRubyArt the decent thing would be create an interface? Use of `java.awt.Robot` under the hood may also be somewaht dodgy, especially since all exceptions get ignored (expected to throw security exception on X windows). It might be ineresting waht could be done in `pure` ruby well at least using `Vec3D` instead of `PVector`.
+It is an unfortunate fact that queasycam uses `processing.core.PVector` under the hood, this does not play too well with JRubyArt the decent thing would be to create an interface? The use of `java.awt.Robot` under the hood may also be somewaht dodgy, especially since all exceptions get ignored (expected to throw security exception on X windows). It might be ineresting waht could be done in `pure` ruby well at least using `Vec3D` instead of `PVector`.

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,3 @@`
`1`	`1`	`### READ ME ###`
`2`	`2`
`3`		-It is an unfortunate fact that queasycam uses `processing.core.PVector` under the hood, this does not play too well with JRubyArt the decent thing would be create an interface? Use of `java.awt.Robot` under the hood may also be somewaht dodgy, especially since all exceptions get ignored (expected to throw security exception on X windows). It might be ineresting waht could be done in `pure` ruby well at least using `Vec3D` instead of `PVector`.
	`3`	+It is an unfortunate fact that queasycam uses `processing.core.PVector` under the hood, this does not play too well with JRubyArt the decent thing would be to create an interface? The use of `java.awt.Robot` under the hood may also be somewaht dodgy, especially since all exceptions get ignored (expected to throw security exception on X windows). It might be ineresting waht could be done in `pure` ruby well at least using `Vec3D` instead of `PVector`.