diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 8a97357..dc914a8 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -18,7 +18,6 @@ env:
 
 jobs:
   test:
-    if: ${{ !(github.event_name == 'pull_request' && github.event.pull_request.base.repo.full_name == github.repository) }}
     runs-on: ubuntu-22.04
     services:
       mssql:
@@ -68,7 +67,6 @@ jobs:
           COVERALLS_PARALLEL: true
 
   coveralls:
-    if: ${{ !(github.event_name == 'pull_request' && github.event.pull_request.base.repo.full_name == github.repository) }}
     name: Finish Coveralls
     needs: test
     runs-on: ubuntu-22.04
diff --git a/README.rst b/README.rst
index 097bee8..eaefbb8 100644
--- a/README.rst
+++ b/README.rst
@@ -11,7 +11,7 @@ asyncodbc
 with asyncio_. It relies on the awesome pyodbc_ library and preserves the same look and
 feel. *asyncodbc* was written using `async/await` syntax (PEP492_) and only support
 Python that is not end-of-life(EOL).  Internally *asyncodbc* employs threads to avoid
-blocking the event loop, threads_ are not that as bad as you think!. Other
+blocking the event loop, threads_ are not that as bad as you think! Other
 drivers like motor_ use the same approach.
 
 **asyncodbc** is fully compatible and tested with uvloop_. Take a look at the test
@@ -39,7 +39,6 @@ Properties are unchanged, so ``conn.prop`` is correct as well as
     import asyncio
     import asyncodbc
 
-
     async def test_example():
         dsn = 'Driver=SQLite;Database=sqlite.db'
         conn = await asyncodbc.connect(dsn=dsn, loop=loop)
@@ -65,7 +64,6 @@ Connection pooling is ported from aiopg_ and relies on PEP492_ features:
     import asyncio
     import asyncodbc
 
-
     async def test_pool():
         dsn = 'Driver=SQLite;Database=sqlite.db'
         pool = await asyncodbc.create_pool(dsn=dsn, loop=loop)
@@ -93,7 +91,6 @@ protocol:
     import asyncio
     import asyncodbc
 
-
     async def test_example():
         dsn = 'Driver=SQLite;Database=sqlite.db'