Skip to content
Browse files

s/existent/existing/

  • Loading branch information...
1 parent a87c263 commit 5d680fe023e44478e1fe6de6fc55644009bb9b44 @miyagawa miyagawa committed
Showing with 3 additions and 3 deletions.
  1. +2 −2 FAQ.pod
  2. +1 −1 PSGI.pod
View
4 FAQ.pod
@@ -80,7 +80,7 @@ framework users will enjoy is huge.
=head3 I'm writing a web application. What's the benefit of PSGI for me?
If the framework you're using supports PSGI, that means your
-application can run on any of existent and future PSGI
+application can run on any of existing and future PSGI
implementations.
if you provide a C<.psgi> file that returns PSGI application,
@@ -100,7 +100,7 @@ environments.
If you're a web application developer (or a web application framework
user), choose the framework that supports PSGI, or ask the author to
support it. :) If your application is a large scale installable
-application that doesn't use any existent frameworks (e.g. WebGUI or
+application that doesn't use any existing frameworks (e.g. WebGUI or
Movable Type) you're considered as a framework developer instead from
the PSGI point of view. So, writing an adapter for PSGI on your
application would make more sense.
View
2 PSGI.pod
@@ -389,7 +389,7 @@ C<$/> value.
=head2 Middleware
-Middleware is itself a PSGI application but it takes an existent PSGI
+Middleware is itself a PSGI application but it takes an existing PSGI
application and runs it like a server, mostly to do pre-processing on
C<$env> or post-processing on the response objects.

0 comments on commit 5d680fe

Please sign in to comment.
Something went wrong with that request. Please try again.