[WIP]Updated the seed file to reflect new text per issue #342, have to che…

[rich-allen-gov]

I've updated the seed file, will also need to provide a migration to actually update the data.

Checklist

I have…

• run the application locally (bin/rails server) and verified that my changes behave as expected.
• run static code analysis (bin/rubocop) and vulnerability scan (bin/brakeman) against my changes.
• run the test suite (bin/rake spec) and verified that all tests pass.
• summarized below my changes and noted which issues (if any) this pull request fixes or addresses.
• thoroughly outlined below the steps necessary to test my changes.
• attached screenshots illustrating relevant behavior before and after my changes.
• read, understand, and agree to the terms described in CONTRIBUTING.md.
• added my name, email address, and copyright date to CONTRIBUTORS.md.

Summary of Changes

#342

Testing

[WIP] Will provide screenshots. Automated testing will be passing.

Screenshots

Attach relevant before and after screenshots here.

[jgarber623-gov]

I've updated the seed file, will also need to provide a migration to actually update the data.

@rich-allen-gov Based on the… unique… way we're handling seed data (documented on this wiki page), you shouldn't have to worry about a migration.

☝️ Note the caveats on that wiki page about how we're using seed data versus how it's supposed to be used.

[rich-allen-gov]

Gotcha, thanks saved some effort there! I'll just go ahead and get the screenshots and package this up for review.

[rich-allen-gov]

For now I will close this, and create new pr with my branch that I pushed direct to the repo.

I went ahead and created #372 which should fix this going forward if we can merge it in.