Fix import, README update

README.md

@@ -7,12 +7,12 @@
 
 > We're back with improvements! See [CHANGES.md](CHANGES.md)
 
-This service forwards domains using 301 HTTP(s) redirects by default.
+This service forwards domains using HTTP(s) redirects.
 
-Possible scenarios:
+Example scenarios:
 
-+ Forward non-www to www URLs or inversely
-+ Forward old URLs to new URLs
++ Forward non-www to www domains or vice versa
++ Forward old domains to new domains
 
 Why using this service?
 
@@ -22,7 +22,7 @@ Why using this service?
 + Completely anonymous
 + Completely free
 
-How it is possible?
+How does it works?
 
 + Point your domain to us using CNAME or A/AAAA records
 + Tell us where to forward using TXT records
@@ -47,7 +47,7 @@ _.old.com   IN    TXT     forward-domain=https://new.net/*
 
 The star `*` at the end tells us that the remaining URL path is also forwarded to the destination URL.
 
-> If you use Cloudflare or any DNS which supports [CNAME Flattening](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/), you still can use CNAME records pointing to `r.forwarddomain.net`, it's much recommended to use CNAME records rather than A/AAAA records.
+> If you use Cloudflare or any DNS which supports [CNAME Flattening](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/), you still can use CNAME records pointing to `r.forwarddomain.net`. It's recommended to use CNAME records rather than A/AAAA records.
 
 You can choose the type of redirection you want to use by declaring the `http-status` value:
 
@@ -56,7 +56,7 @@ www.old.com     IN    CNAME   r.forwarddomain.net
 _.www.old.com   IN    TXT     http-status=302;forward-domain=https://old.com/*
 ```
 
-> Only the http status code 301 and 302 are supported.
+> Only the HTTP status code 301 and 302 are supported. By default it's 301, which is permanent redirection. Set to 302 if you want temporary redirection, it has effect on search engine indexing.
 
 ## FAQ