There are two specific files when you're looking at the context of an alarm in the OneClick console.
Event File (contains trap based information)
PCause File (contains Alarm Title, Symptoms, Probable Cause, Recommended Actions)
The default location for these are <SPECROOT>/SG-Support/CsEvFormat and <SPECROOT>/SG-Support/CsPCause.
If you want to modify the specific files within the example, copy them into the corresponding custom directory:
<SPECROOT>/custom/Events/CsEvFormat
<SPECROOT>/custom/Events/CsPCause
Looks like the default behavior for event 0x00210d53 is simply a logged event. If you turned this into an alarm within an EventDisp file, you'll need to create a PCause file and stick it in custom. I'm guessing this is what you did since your Probable Cause says "SPC-SAN-20041: No Associated Text"
You can edit the Event or PCause files to make them more legible for you. Just remember to use the custom directory that way your changes won't get overwritten on a Spectrum patch/upgrade.
Oh, remember to reload the events within the administrative web page for your OneClick server:
Administration --> Update Event and Alarm Files --> Click "Reload".