Add suggested extra issue and adjust the Expected Outcomes

documentation/projects/proposals/data_normalization/20240227-implementation_plan_catalog_data_cleaning.md

@@ -52,8 +52,8 @@ permanent by saving them in the upstream database.
 
 - The catalog database (upstream) contains the cleaned data outputs of the
   current Ingestion Server's cleaning steps
-- The image Data Refresh process is simplified by reducing the cleaning steps
-  time to nearly zero (and optionally removing them).
+- The image Data Refresh process is simplified by removing the cleaning steps
+  from the Ingestion Server.
 
 ## Step-by-step plan
 
@@ -163,6 +163,8 @@ related issues are:
 - [Some images have duplicate incorrectly decoded unicode tags #1303](https://github.com/WordPress/openverse/issues/1303)
 - [Provider scripts may include html tags in record titles #1441](https://github.com/WordPress/openverse/issues/1441)
 - [Fix Wikimedia image titles #1728](https://github.com/WordPress/openverse/issues/1728)
+- [Add filetype to all images in the catalog DB #1560](https://github.com/WordPress/openverse/issues/1560),
+  for when the file type can be derived from the URL.
 
 This will also open up space for more structural changes to the Openverse DB
 schemas in a [second phase](https://github.com/WordPress/openverse/issues/244)