Formatting

svn-id: r49233

1 files changed, 5 insertions, 5 deletions

diff --git a/engines/sci/engine/vm.cpp b/engines/sci/engine/vm.cpp
index 8ee60874ea..44279af1c1 100644
--- a/engines/sci/engine/vm.cpp
+++ b/engines/sci/engine/vm.cpp
@@ -414,11 +414,11 @@ ExecStack *send_selector(EngineState *s, reg_t send_obj, reg_t work_obj, StackPt
 			if (argc > 1) {
 				// argc can indeed be bigger than 1 in some cases, and it seems correct
 				// (i.e. we should skip that many bytes later on)... question is, why
-				// does this occur? Could such calls be used to point to data after X bytes in the heap?
-				// What are the skipped bytes in this case?
-				// In SQ4CD, this occurs with the returnVal selector of object Sq4GlobalNarrator when the
-				// game starts, and right after the narrator is heard (e.g. after he talks when examining
-				// something)
+				// does this occur? Could such calls be used to point to data after X
+				// bytes in the heap? What are the skipped bytes in this case?
+				// In SQ4CD, this occurs with the returnVal selector of object
+				// Sq4GlobalNarrator when the game starts, and right after the narrator
+				// is heard (e.g. after he talks when examining something)
 				reg_t oldReg = *varp.getPointer(s->_segMan);
 				reg_t newReg = argp[1];
 				warning("send_selector(): argc = %d while modifying variable selector "