BUG: Typos in search instructions

[klohman]

Describe the Bug
Typos found in Order search instructions PDF

Business Impact/Reason for Severity

In which environment did you see this bug?
prod

Who were you logged in as?
court user

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)

To Reproduce
Steps to reproduce the behavior:

1. Go to Order search
2. click PDF link for search instructions

Expected Behavior
No typos in PDF

Actual Behavior
Typos in PDF

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Cause of Bug, If Known

Process for Logging a Bug:

• Complete the above information
• Add a severity tag (Critical, High Severity, Medium Severity or Low Severity). See below for priority definition.

Severity Definition:

• Critical Defect
  Blocks entire system's or module’s functionality
  No workarounds available
  Testing cannot proceed further without bug being fixed.

• High-severity Defect
  Affects key functionality of an application
  There's a workaround, but not obvious or easy
  App behaves in a way that is strongly different from the one stated in the requirements

• Medium-severity Defect
  A minor function does not behave in a way stated in the requirements.
  Workaround is available and easy

• Low-severity Defect
  Mostly related to an application’s UI
  Doesn't need a workaround, because it doesn't impact functionality

Definition of Done (Updated 4-14-21)

Product Owner

• Bug fix has been validated in the Court's test environment

Engineering

• Automated test scripts have been written
• Field level and page level validation errors (front-end and server-side) integrated and functioning
• Verify that language for docket record for internal users and external users is identical
• New screens have been added to pa11y scripts
• All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
• READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
• UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
• Interactors should validate entities before calling persistence methods
• Code refactored for clarity and to remove any known technical debt
• Deployed to the Court's test environment

[klohman]

Search Examples PDF_8-30-21.pdf

[matthopson]

@klohman It looks like you were maybe trying to upload a PDF here? ☝️

[matthopson]

@mmarcotte We're going to need to get the test env updated with prod before this can be addressed. This will technically be a blocker.

[ttlenard]

Just reviewed this over on TEST. The updates to the document look great. Thank you for fixing those!