From 2aa80312465400544681a3bbdcf60cca19a330f8 Mon Sep 17 00:00:00 2001 From: Uzair Isap Date: Thu, 7 Sep 2017 17:54:46 +0100 Subject: [PATCH 1/2] README.md Sentence structure improvement Fixed the sentence structure to make it easier to read. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 280287a..5d3fa73 100644 --- a/README.md +++ b/README.md @@ -49,7 +49,7 @@ Another algorithm name is supported: ```` This will use the strongest algorithm available to PHP at the current time. Presently, this is the same as specifying `PASSWORD_BCRYPT`. But in future versions of PHP, it may be updated to use a stronger algorithm if one is introduced. It can also be changed if a problem is identified with the BCRYPT algorithm. Note that if you use this option, you are **strongly** encouraged to store it in a `VARCHAR(255)` column to avoid truncation issues if a future algorithm increases the length of the generated hash. -It is very important that you should check the return value of `password_hash` prior to storing it, because `false` or `null` may be returned if it encountered an error. +It is very important that you check the return value of `password_hash` prior to storing it, because `false` or `null` may be returned if it encountered an error. **Verifying Password Hashes** From 9c252a7eda5caafed60611bc6d5791b1ebcf1fda Mon Sep 17 00:00:00 2001 From: Uzair Isap Date: Thu, 7 Sep 2017 17:56:54 +0100 Subject: [PATCH 2/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5d3fa73..8bef73d 100644 --- a/README.md +++ b/README.md @@ -49,7 +49,7 @@ Another algorithm name is supported: ```` This will use the strongest algorithm available to PHP at the current time. Presently, this is the same as specifying `PASSWORD_BCRYPT`. But in future versions of PHP, it may be updated to use a stronger algorithm if one is introduced. It can also be changed if a problem is identified with the BCRYPT algorithm. Note that if you use this option, you are **strongly** encouraged to store it in a `VARCHAR(255)` column to avoid truncation issues if a future algorithm increases the length of the generated hash. -It is very important that you check the return value of `password_hash` prior to storing it, because `false` or `null` may be returned if it encountered an error. +It is very important that you check the return value of `password_hash` prior to storing it, because `false` or `null` may be returned if it encounters any errors. **Verifying Password Hashes**