Index: uspace/srv/fs/minixfs/mfs.c
===================================================================
--- uspace/srv/fs/minixfs/mfs.c	(revision 6a8d265912860ff3b573d6458bea0d79607de0b3)
+++ uspace/srv/fs/minixfs/mfs.c	(revision fd7f329a81c314daa389df5bacab3b127ba88005)
@@ -68,5 +68,5 @@
  * The connection fibril accepts VFS requests from VFS. If there is only one
  * instance of the fibril, VFS will need to serialize all VFS requests it sends
- * to FAT. To overcome this bottleneck, VFS can send FAT the IPC_M_CONNECT_ME_TO
+ * to MinixFS. To overcome this bottleneck, VFS can send MinixFS the IPC_M_CONNECT_ME_TO
  * call. In that case, a new connection fibril will be created, which in turn
  * will accept the call. Thus, a new phone will be opened for VFS.
@@ -74,8 +74,8 @@
  * There are few issues with this arrangement. First, VFS can run out of
  * available phones. In that case, VFS can close some other phones or use one
- * phone for more serialized requests. Similarily, FAT can refuse to duplicate
+ * phone for more serialized requests. Similarily, MinixFS can refuse to duplicate
  * the connection. VFS should then just make use of already existing phones and
  * route its requests through them. To avoid paying the fibril creation price 
- * upon each request, FAT might want to keep the connections open after the
+ * upon each request, MinixFS might want to keep the connections open after the
  * request has been completed.
  */
@@ -125,4 +125,5 @@
 		goto err;
 
+	/* not reached */
 	return 0;