diff --git a/.github/workflows/build_run_unit_test_cmake.yml b/.github/workflows/build_run_unit_test_cmake.yml
index 2186356..6b3b1dc 100644
--- a/.github/workflows/build_run_unit_test_cmake.yml
+++ b/.github/workflows/build_run_unit_test_cmake.yml
@@ -24,7 +24,8 @@ jobs:
       - name: create-build-dir
         run: mkdir build
       - name: configure-cmake
-        run: cd build && cmake -D SHARED_BUFFER_BUILD_TESTS:BOOL=ON -D SHARED_BUFFER_BUILD_EXAMPLES:BOOL=ON ..
+         #run: cd build && cmake -D SHARED_BUFFER_BUILD_TESTS:BOOL=ON -D SHARED_BUFFER_BUILD_EXAMPLES:BOOL=ON ..
+        run: cd build && cmake -D SHARED_BUFFER_BUILD_TESTS:BOOL=ON ..
       - name: build
         run: cd build && cmake --build . --config $BUILD_TYPE
       - name: run-unit-test
diff --git a/README.md b/README.md
index 4135cc6..e379010 100644
--- a/README.md
+++ b/README.md
@@ -16,7 +16,7 @@
 
 The `shared_buffer` classes are reference counted `std::byte` buffer classes useful for asynchronous networking. In particular, the Asio asynchronous networking library requires a buffer to be kept alive and valid until the outstanding IO operation (e.g. a network write) is completed. A straightforward and idiomatic way to achieve this is by using reference counted buffers.
 
-There are two classes - `const_shared_buffer` for outgoing buffers (which should not be modified), and `mutable_shared_buffer` for incoming buffers (mutable and expandable as data arrives). In addition there are efficient (move) operations for creating a `const_shared_buffer` from a `mutable_shared_buffer`. This allows the following use common networking use case: create a `mutable_shared_buffer`, serialize objects into it, then (efficiently) construct a `const_shared_buffer` and send it out over the network.
+There are two classes - `const_shared_buffer` for outgoing buffers (which should not be modified), and `mutable_shared_buffer` for incoming buffers (mutable and expandable as data arrives). In addition there are efficient (move) operations for creating a `const_shared_buffer` from a `mutable_shared_buffer`. This allows the following common networking use case: create a `mutable_shared_buffer`, serialize objects into it, then (efficiently) construct a `const_shared_buffer` and send it out over the network.
 
 While internally all data is kept in `std::byte` buffers, convenience methods are provided for converting between traditional buffer types (such as `char *` or `unsigned char*` or similar).
 
diff --git a/example/CMakeLists.txt b/example/CMakeLists.txt
index fcab5f9..7a9fbee 100644
--- a/example/CMakeLists.txt
+++ b/example/CMakeLists.txt
@@ -12,7 +12,7 @@ project ( shared_buffer_example LANGUAGES CXX )
 include ( ../cmake/download_cpm.cmake )
 
 CPMAddPackage ( "gh:connectivecpp/utility-rack@1.0.6" )
-CPMAddPackage ( "gh:connectivecpp/binary-serialize@1.0.4" )
+CPMAddPackage ( "gh:connectivecpp/binary-serialize@1.0.5" )
 
 # add executable
 add_executable ( shared_buffer_example shared_buffer_example.cpp )