<p>For example, if we used <b>GET</b> requests then the token would appear as
part of a URL, where it would end up being written in the location bar of
-many browsers, stored in history databases, many even sent to random cloud
+many browsers, stored in history databases, maybe even sent to random cloud
services; this obviously has an adverse effect on security. Also, the token
is kind of long and ugly.
that causes other trouble. In particular, you’d get that annoying
<blockquote>
The page that you’re looking for used information that you
- entered. Returning to hat page might cause any action that you took to be
- repeated.
+ entered. Returning to that page might cause any action that you took
+ to be repeated.
</blockquote>
message whenever you hit the reload button.