Less lulz (#52)

* Less lulz

.github/workflows/test.yml

@@ -14,16 +14,14 @@ jobs:
 
     steps:
     - uses: actions/checkout@v1
-    - name: Install swiftenv
-      run: eval "$(curl -sL https://swiftenv.fuller.li/install.sh)";
-    - name: Install FoundationDB
+    - name: Run tests
       run: |
-        apt-get install -y wget
+        eval "$(curl -sL https://swiftenv.fuller.li/install.sh)"
+        sudo apt-get install -y wget
         wget https://www.foundationdb.org/downloads/6.0.18/ubuntu/installers/foundationdb-clients_6.0.18-1_amd64.deb
         wget https://www.foundationdb.org/downloads/6.0.18/ubuntu/installers/foundationdb-server_6.0.18-1_amd64.deb
-        dpkg -i foundationdb-clients_6.0.18-1_amd64.deb foundationdb-server_6.0.18-1_amd64.deb
-        service foundationdb start
+        sudo dpkg -i foundationdb-clients_6.0.18-1_amd64.deb foundationdb-server_6.0.18-1_amd64.deb
+        sudo service foundationdb start
         chmod +x scripts/install_pkgconfig.sh
-        ./scripts/install_pkgconfig.sh
-    - name: Run tests
-      run: swift test
+        sudo ./scripts/install_pkgconfig.sh
+        swift test

README.md

@@ -33,7 +33,7 @@ By default (and in the very core) this wrapper, as well as C API, operates with
 
 Values are always bytes (`typealias Bytes = [UInt8]`) (or `nil` if key not found). Why not `Data` you may ask? I'd like to stay `Foundation`less for as long as I can (srsly, import half of the world just for `Data` object which is a fancy wrapper around `NSData` which is a fancy wrapper around `[UInt8]`?) (Hast thou forgot that you need to wrap all your `Data` objects with `autoreleasepool` or otherwise you get _fancy_ memory leaks?) (except for Linux tho, yes), you can always convert bytes to `Data` with `Data(bytes: myBytes)` initializer (why would you want to do that? oh yeah, right, JSON... ok, but do it yourself plz, extensions to the rescue).
 
-Ahem. Where was I? OK so about library API. First let's deal with synchronous API (there is also asynchronous, using Swift-NIO, see below).
+First let's deal with synchronous API (there is also asynchronous, using Swift-NIO, see below).
 
 ### Connection