X-Git-Url: https://www.bearssl.org/gitweb//home/git/?p=BearSSL;a=blobdiff_plain;f=README.txt;h=0cb5288740669690d2a0dea90dd0c3085bd84a8c;hp=a440e294a2178696ddb1f5ef46a16e1fd16c55d1;hb=15b3af72f3220cae0bba4080db653d0124bf9414;hpb=3f00688b9d9f483a6ca97e659eea104995ea15b7

diff --git a/README.txt b/README.txt
index a440e29..0cb5288 100644
--- a/README.txt
+++ b/README.txt
@@ -5,15 +5,16 @@ The most up-to-date documentation is supposed to be available on the
 
 # Disclaimer
 
-BearSSL is for now considered alpha-level software. This means that it
-probably still has some bugs, possibly very serious ones (e.g. buffer
-overflows -- one of the perks of using C as programming language). It
-still lacks some functionalities. The API will probably change and may
-break both source and binary compatibility.
+BearSSL is considered beta-level software. Most planned functionalities
+are implemented; new evolution may still break both source and binary
+compatibility.
 
-In other words, you would be quite mad to use it for any production
-purpose. Right now, this is for learning, testing and possibly
-contributing.
+Using BearSSL for production purposes would be a relatively bold but not
+utterly crazy move. BearSSL is free, open-source software, provided
+without any guarantee of fitness or reliability. That being said, it
+appears to behave properly, and only minor issues have been found (and
+fixed) so far. You are encourage to inspect its API and code for
+learning, testing and possibly contributing.
 
 The usage license is explicited in the `LICENSE.txt` file. This is the
 "MIT license". It can be summarised in the following way:
@@ -112,7 +113,7 @@ Dependencies are simple and systematic:
 
 I follow this simple version numbering scheme:
 
- - Version numbers are `x.y` or `x.y.z` where `x`, `y` ans `z` are
+ - Version numbers are `x.y` or `x.y.z` where `x`, `y` and `z` are
    decimal integers (possibly greater than 10). When the `.z` part is
    missing, it is equivalent to `.0`.