Update changelog for release 0.3.0

Author: Tim Bruijnzeels

Changelog.md

@@ -5,7 +5,7 @@ for planned releases.
 
 ## 0.3.0 'The Krilling is on the wall'
 
-This release focused on publication.
+This release focused on remote publication.
 
 You can now use Krill as an RFC8181 compliant Repository Server. If you want to use it as a dedicated
 repository server only, you can simply do this by not configuring any CAs in that particular instance.
@@ -15,11 +15,13 @@ useful if you want to outsource the responsibility of 24/7 availability of your
 to a third party.   
 
 We have also made some breaking changes to the API. So, you may have to look again at any
-automation you may have set previously up for version 0.2.0.
+automation you may have set previously up for release 0.2.0.
 
-The known issue where Krill CAs and their publication server may become out-of-sync after
-restarts has been solved. Krill CAs will always perform a check when publishing, and if needed
-to do full re-syncs.
+Updated documentation can be found on [Read the Docs](https://rpki.readthedocs.io/en/latest/krill/index.html).
+
+Two of the known issues listed under release 0.2.0 have been solved:
+ * CAs now do full re-syncs when publishing (solves #116)
+ * RIPE NCC RPKI Validator 3.1 now validates our objects (solves #115) 
 
 The next release of Krill is aimed for early December and will focus fully on stability, and the
 other known issues listed under release 0.2.0. But, note that there may still be small API changes