From 171c24a24b31ced6e6e4e319e8cc520856a9cb86 Mon Sep 17 00:00:00 2001 From: Richard Imaoka Date: Mon, 7 Mar 2016 07:11:47 +0000 Subject: [PATCH] Fix typo #19898 --- akka-docs/rst/scala/http/introduction.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/akka-docs/rst/scala/http/introduction.rst b/akka-docs/rst/scala/http/introduction.rst index 01225e7579..64d07e1b3f 100644 --- a/akka-docs/rst/scala/http/introduction.rst +++ b/akka-docs/rst/scala/http/introduction.rst @@ -10,7 +10,7 @@ You get to pick the API level of abstraction that is most suitable for your appl This means that, if you have trouble achieving something using a high-level API, there's a good chance that you can get it done with a low-level API, which offers more flexibility but might require you to write more application code. -Phylosophy +Philosophy --------------- Akka HTTP has been driven with a clear focus on providing tools for building integration layers rather than application cores. As such it regards itself as a suite of libraries rather than a framework.