Correct code does not pass in 'Nest an Anchor' waypoint

[riteshshrv]

Challenge Waypoint: Nest an Anchor Element within a Paragraph has an issue.
User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

<link href="http://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">
<style>
  .red-text {
    color: red;
  }

  h2 {
    font-family: Lobster, Monospace;
  }

  p {
    font-size: 16px;
    font-family: Monospace;
  }

  .thick-green-border {
    border-color: green;
    border-width: 10px;
    border-style: solid;
    border-radius: 50%;
  }

  .smaller-image {
    width: 100px;
  }
</style>

<h2 class="red-text">CatPhotoApp</h2>

<a href="http://www.freecatphotoapp.com">cat photos</a>

<img class="smaller-image thick-green-border" src="https://bit.ly/fcc-relaxing-cat">

<p class="red-text">Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>
<p class="red-text">Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.</p>
<p>View more <a href="http://www.freecatphotoapp.com">cat photos</a></p>

[ltegman]

This challenge is asking to you wrap the existing <a> tag that is right below the <h2>, not create a new one at the bottom. The test expects to find your <p> up there with the original <a>, so adding it down at the bottom causes the test to fail.

However, this is the third time in a week or so that I've seen this same issue reported, so I propose adding some clarifying language to the waypoint that lets the user know they should not be moving existing <a> tag, only wrapping it.

[riteshshrv]

It worked. Indeed the language should be more clarifying.

[idanceicode]

Great, just reading your your response. Unsure if you have added clarifying language yet but I have run into the same isue...as of two days ago, 10/21...

[ltegman]

The change has been pulled into the staging branch but hasn't been pushed into the production code yet. It shouldn't be too long before it is.