Issue 1:
Here's the tweet with the video capture of this bug in action: https://twitter.com/ianothere/status/684476677632606208

Challenge Waypoint: Target HTML Elements with Selectors Using jQuery has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

<script>
$(document).ready(function() {
$("button").addClass("animated bounce");
$($("button"))
});
while (true) {

}
</script>

<!-- You shouldn't need to modify code below this line -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>

Issue 2:
I updated the Issue Template with #7958 and I feel the Pull Request Template could use an update too. This website can autogenerate a template by asking you a series of questions on what you need in a PR and it'll generate a template for you. Here's the template I got:

<!--- Provide a general summary of your changes in the Title above -->

## Description
<!--- Describe your changes in detail -->

## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
<!--- If it fixes an open issue, please link to the issue here. -->

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->

## Screenshots (if appropriate):

## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)

## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [x] My change requires a change to the documentation.
- [x] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.

The reason I am for checklists for PRs is because we ask things like if you've tested locally or not. Rather than type it every time, you can just add an x to cross it off.

New Template

I propose the following as the new template. I've removed a lot of instructions from the current template as Camperbot takes care of a lot of them, like make sure you only have one commit. Any feedback is welcome.

<!-- FreeCodeCamp Pull Request Template -->

<!-- IMPORTANT Please review the https://github.com/FreeCodeCamp/FreeCodeCamp/blob/staging/CONTRIBUTING.md for detailed contributing guidelines -->
<!-- Make sure that you PR is not a duplicate -->

## Pre-Submission Checklist
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- All of these points should be checked, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] Branches much start with either `fix/` or `feature/`
- [ ] You have only one commit (if not, [squash](https://github.com/FreeCodeCamp/ FreeCodeCamp/wiki/git-rebase#squashing-multiple-commits-into-one) them into one commit).
- [ ] All new and existing tests pass `npm run test-challenges`.

## Description
<!-- Describe your changes in detail -->

## Types of changes
<!-- What types of changes does your code introduce? Put one `x` in the box that applies. -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] Add new translation (feature adding new translations)

## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] Tested changes locally.
- [ ] Closes currently open issue (`Closes #XXXX`): Closes

New Template Rendered

Pre-Submission Checklist

Branches much start with either fix/ or feature/

You have only one commit (if not, [squash](https://github.com/FreeCodeCamp/ FreeCodeCamp/wiki/git-rebase#squashing-multiple-commits-into-one) them into one commit).

All new and existing tests pass npm run test-challenges.

Description

Types of changes

Bug fix (non-breaking change which fixes an issue)

New feature (non-breaking change which adds functionality)

Breaking change (fix or feature that would cause existing functionality to change)

Add new translation (feature adding new translations)

Checklist:

Tested changes locally.

Closes currently open issue (Closes #XXXX): Closes