Standardized CENTCOM spelling

code/modules/research/rdconsole.dm

@@ -20,7 +20,7 @@ this dire fate:
 it's data to every other device in the game. Each console has a "disconnect from network" option that'll will cause data base sync
 operations to skip that console. This is useful if you want to make a "public" R&D console or, for example, give the engineers
 a circuit imprinter with certain designs on it and don't want it accidentally updating. The downside of this method is that you have
-to have physical access to the other console to send data back. Note: An R&D console is on Centcom so if a random griffan happens to
+to have physical access to the other console to send data back. Note: An R&D console is on CentCom so if a random griffan happens to
 cause a ton of data to be lost, an admin can go send it back.
 - The second method is with Technology Disks and Design Disks. Each of these disks can hold technology or design datums in
 their entirety. You can then take the disk to any R&D console and upload it's data to it. This method is a lot more secure (since it

code/modules/research/research.dm

@@ -349,7 +349,7 @@ research holder datum.
 	max_tech_stored = 10
 
 /obj/item/weapon/disk/tech_disk/debug
-	name = "centcomm technology disk"
+	name = "centcom technology disk"
 	desc = "A debug item for research"
 	materials = list()
 	max_tech_stored = 0

code/modules/research/server.dm

@@ -133,7 +133,7 @@
 	return
 
 /obj/machinery/r_n_d/server/centcom
-	name = "Centcom Central R&D Database"
+	name = "CentCom Central R&D Database"
 	server_id = -1
 
 /obj/machinery/r_n_d/server/centcom/Initialize()