Updated changelog and read me

M66B · Feb 13, 2014 · 576f421 · 576f421
1 parent 13d5205
commit 576f421
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 7 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -7,12 +7,6 @@ Changelog
 * BETA: new or updated features with a lower risk for bugs
 * STABLE: all known bugs fixed; low risk for bugs
 
-Test and beta releases will have experimental functions enabled by default.
-
-**Experimental functions**
-
-* None at this time
-
 **Next release**
 
 [Open issues](https://github.com/M66B/XPrivacy/issues?state=open)

diff --git a/README.md b/README.md
@@ -279,7 +279,6 @@ Limitations
 * You cannot restrict *system* fro XPrivacy because it is needed to get an application list.
 * You cannot restrict *view* for XPrivacy because it is needed to open links to the crowdsourced restrictions.
 * You cannot restrict *Configuration.MCC/MNC* on demand.
-* Allowing contacts mostly work, but there are a few corner cases where is doesn't ([issue](https://github.com/M66B/XPrivacy/issues/1155)).
 * Allowing contacts for SIM-contacts isn't supported (who is using these anyway these days?).
 
 You can still restrict the XPrivacy app's access to accounts, contacts, and other things.
@@ -667,6 +666,11 @@ No, the pro license can be used independently.
 
 Yes, it is not feasible to add other donation methods at this moment.
 
+<a name="FAQ37"></a>
+**(37)What are the experimental functions?**
+
+None at this time.
+
 <a name="FAQ46"></a>
 **(46) Why do I need to register to submit restrictions?**