Fix small bugs

media/manual.txt

@@ -297,13 +297,31 @@ much.
 
 Q: Why is the physics so buggy?
 
-A: You are right in the observation that Licar physics is not perfect. This is
+A: You are correct in the observation that Licar physics is not perfect. This is
 firstly because of the game's aim for simplicity (e.g. avoiding use of floating
 point) combined with the fact that even without such constraints it's one of the
-most difficult tasks to create a flawless physics engine. We apologize for any
+most difficult tasks to create a flawless physics engine. I apologize for any
 frustration but unless you want to fix this yourself, you'll have to just accept
-it, the game is meant to be a simple entertainment. In other words this is a
-feature :)
+it, the game is meant to be a simple entertainment, not physically realistic
+simulator. After the release of the game it's also difficult to make any changes
+to physics because all previous replays will get invalidated by the change, so
+changing anything about physics will be done very, very rarely.
+
+Q: The graphics looks weird, stuff near camera seems to kind of warp weirdly.
+
+A: It's a feature, this is the software renderer's simplification of handling
+near plane culling, it's how it was done back in the era of PS1 and similar
+consoles, it has its charm. It should be possible to turn on the "correct",
+non-warping way somewhere in the code (S3L_NEAR_CROSS_STRATEGY) if you really
+want to, but it will cost some FPS.
+
+Q: I see glitching triangles suddenly flashing over the screen.
+
+A: This may be happening in higher resolutions, it's because of overflows in
+integer math. Effort was made to minimize this but it can probably still happen
+at times. Lowering the resolution should generally help, also increasing
+S3L_NEAR in renderer.h should prevent this (but it will have some consequences).
+If it seems real significant, you can report this to me. 
 
 Q: I found a bug or have some other important comment.
 A: Send me an email (found on top of this file).