up to date

Catalog Items - Flow.md

@@ -8,7 +8,7 @@ Login to your personal developer instance.
 2. Create new
 3. Fill out these values:
 	1. Name: [your name]'s Test Catalog Item
-	2. Catalogs: IT Services Request Catalog
+	2. Catalogs: Pick an existing catalog in the picker
 	3. Category: Student Practice (you might have to make this if someone hasn't already made it for you)
 	4. Short Description: A catalog item designed for practicing servicenow admin fundamental skills
 	5. Portal Settings, Request method: Submit

Standards/Update Sets.md

@@ -1,5 +1,7 @@
 # Update Sets 
 
+Remember: different companies do things differently! The below doesn't necessarily apply to every dev team.
+
 ### Update Set Naming Conventions 
 
 Use a consistent naming convention for update sets. 
@@ -18,8 +20,9 @@ org_reference_desc_seq/date
 
 ### Good Practices for Update Sets 
 
-- Never delete an Update Set. 
+- Never delete an Update Set. (Some companies delete them in production though, YMMV)
 - Never re-open previously completed update sets. Create new ones instead. 
+  - Why? If another instance has retrieved your update set already then it will never try to retrieve your newly "updated" update set, resulting in desynced update sets.
 - Never manually merge update sets. Utilize batch functionality instead. 
 - Before completing an update set, review the update set to ensure that the only updates included pertain to the desired work. 
 - Preview update sets before committing them. 
@@ -32,4 +35,4 @@ org_reference_desc_seq/date
 ### Instance Administrators
 
 - When preparing for production release, batch all updates for that release together
-- When pulling to production, delete all irrelevant update sets from the loaded table
+- When pulling to production, delete all irrelevant update sets from the loaded table