diff --git a/external_library/java/queasycam/README.md b/external_library/java/queasycam/README.md
index da65d11..5e4d7a2 100644
--- 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 PVector under the hood, this does not play too well with JRubyArt the decent thing would be create an interface?
+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 somewhat dodgy, especially since all exceptions get ignored (_the constructor is expected to throw a security exception on X windows_). It might be interesting what could be done in `pure` ruby well at least using `Vec3D` instead of `PVector`.