-
Notifications
You must be signed in to change notification settings - Fork 807
Fix report grammar and support email in UI #2899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
className='badge badge-info'>{this.state.report.overview.monkey_start_time}</span>. {this.getMonkeyDuration()} | ||
</p> | ||
<p> | ||
The monkey started propagating from the following machines where it was manually installed: | ||
Infection Monkey started propagating from the following machines where it was manually installed: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't here be Agent
?
@@ -196,7 +196,7 @@ class ReportPageComponent extends AuthComponent { | |||
'' | |||
: | |||
<p> | |||
Note: Monkeys were configured to avoid scanning of the local network. | |||
Note: Infection Monkey was configured to avoid scanning the local network. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question as above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be consistent with how we call the agent. We call it monkey or agent or infection monkey agent or what. Either way, a time will come when we'll have to review the whole UI to make sure it's consistent. @ybasford should help, so don't stress about this now, this has little to do with our goal of releasing plugins ASAP
7f33391
to
44a14fb
Compare
What does this PR do?
Minor changes to wording in reports. Updates support email link in report footer.
PR Checklist
Was the documentation framework updated to reflect the changes?Have you checked that you haven't introduced any duplicate code?Testing Checklist
Added relevant unit tests?Have you successfully tested your changes locally? Elaborate:If applicable, add screenshots or log transcripts of the feature working