From af67e996dc93ade1acd4eed47d25da55c0c63b50 Mon Sep 17 00:00:00 2001 From: Christian Cleberg Date: Tue, 11 Nov 2025 20:56:22 -0600 Subject: fix grammar in 2020 posts --- content/blog/2020-08-29-php-auth-flow.org | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'content/blog/2020-08-29-php-auth-flow.org') diff --git a/content/blog/2020-08-29-php-auth-flow.org b/content/blog/2020-08-29-php-auth-flow.org index d1ee5ee..0276c9f 100644 --- a/content/blog/2020-08-29-php-auth-flow.org +++ b/content/blog/2020-08-29-php-auth-flow.org @@ -7,8 +7,9 @@ When creating websites that will allow users to create accounts, the developer always needs to consider the proper authentication flow for their app. For -example, some developers will utilize an API for authentication, some will use -OAuth, and some may just use their own simple database. +example, some developers will utilize an application programming interface (API) +for authentication, some will use OAuth, and some may just use their own simple +database. For those using pre-built libraries, authentication may simply be a problem of copying and pasting the code from their library's documentation. For example, -- cgit v1.2.3