dm vdo: update module comments

Update outdated comments referring to separate VDO and UDS
modules.
Signed-off-by: Matthew Sakai <msakai@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@kernel.org>

drivers/md/dm-vdo/dm-vdo-target.c

@@ -2907,9 +2907,7 @@ static int __init vdo_init(void)
 {
 	int result = 0;
 
-	/*
-	 * UDS module level initialization must be done first, as VDO initialization depends on it
-	 */
+	/* Memory tracking must be initialized first for accurate accounting. */
 	uds_memory_init();
 	uds_init_sysfs();
 
@@ -2917,7 +2915,7 @@ static int __init vdo_init(void)
 	vdo_initialize_device_registry_once();
 	uds_log_info("loaded version %s", CURRENT_VERSION);
 
-	/* Add VDO errors to the already existing set of errors in UDS. */
+	/* Add VDO errors to the set of errors registered by the indexer. */
 	result = vdo_register_status_codes();
 	if (result != UDS_SUCCESS) {
 		uds_log_error("vdo_register_status_codes failed %d", result);
@@ -2939,11 +2937,8 @@ static int __init vdo_init(void)
 static void __exit vdo_exit(void)
 {
 	vdo_module_destroy();
-	/*
-	 * UDS module level exit processing must be done after all VDO module exit processing is
-	 * complete.
-	 */
 	uds_put_sysfs();
+	/* Memory tracking cleanup must be done last. */
 	uds_memory_exit();
 }