Fix typo

billoneil · billoneil · commit 92f0de02febd · 2019-03-18T21:14:34.000-04:00
diff --git a/stubbornjava-webapp/ui/src/posts/database-connection-pooling-in-java-with-hikaricp.hbs b/stubbornjava-webapp/ui/src/posts/database-connection-pooling-in-java-with-hikaricp.hbs
@@ -11,7 +11,7 @@
 <p><A href="https://github.com/brettwooldridge/HikariCP">HikariCP</a> is a very fast lightweight Java connection pool. The API and overall codebase is relatively small (A good thing) and highly optimized. It also does not cut corners for performance like many other Java connection pool implementations. The Wiki is highly informative and dives really deep. If you are not as interested in the deep dives you should at least read and watch the video on <a href="https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing">connection pool sizing.</a></p>
 
 <h2 class="anchored">Creating Connection pools</h2>
-<p>Let's create two connections pools one for OLTP (named transactional) queries and one for OLAP (named processing). We want them split so we can have a queue of reporting queries back up but allow critical transactional queries to still get priority (This is up to the database of course but we can help a bit). We can also easily configure different timeouts or transaction iscolation levels. For now we just just change their names and pool sizes.</p>
+<p>Let's create two connections pools one for OLTP (named transactional) queries and one for OLAP (named processing). We want them split so we can have a queue of reporting queries back up but allow critical transactional queries to still get priority (This is up to the database of course but we can help a bit). We can also easily configure different timeouts or transaction isolation levels. For now we just just change their names and pool sizes.</p>
 
 <h3 class="anchored">Configuring the Pools</h3>
 <p>HikariCP offers several options for configuring the pool. Since we are fans of roll your own and already created our own <a href="/posts/environment-aware-configuration-with-typesafe-config">Typesafe Configuration</a> we will reuse that. Notice we are using some of Typesafe's configuration inheritance.</p>
