Merge pull request #1055 from mattspitz/master

it's => its on the Rate Limiting page

src/sentry/locale/en/LC_MESSAGES/django.po

@@ -1953,7 +1953,7 @@ msgstr ""
 msgid ""
 "Rate limits apply on a per-minute basis, which means that they rollover at "
 "the start of a new minute. When you attempt to send an event and the project "
-"is over it's quota, the client will receive an HTTP 429 (Too Many Requests) "
+"is over its quota, the client will receive an HTTP 429 (Too Many Requests) "
 "response."
 msgstr ""
 

src/sentry/templates/sentry/projects/quotas.html

@@ -13,7 +13,7 @@
     <form action="" method="post" class="form-stacked">
         <p>{% blocktrans %}With the nature of Sentry, sometimes the amount of data collected can be overwhelming. You can set rate limits per-project to ensure that a single flood of errors won't affect any other projects utilizing Sentry.{% endblocktrans %}</p>
 
-        <p>{% blocktrans %}Rate limits apply on a per-minute basis, which means that they rollover at the start of a new minute. When you attempt to send an event and the project is over it's quota, the client will receive an HTTP 429 (Too Many Requests) response.{% endblocktrans %}</p>
+        <p>{% blocktrans %}Rate limits apply on a per-minute basis, which means that they rollover at the start of a new minute. When you attempt to send an event and the project is over its quota, the client will receive an HTTP 429 (Too Many Requests) response.{% endblocktrans %}</p>
 
         {% if not has_quotas %}
             <p><strong>{% blocktrans %}Note: The Sentry application is not configured to manage rate limits.{% endblocktrans %}</strong></p>