From bfcd6b66c6c0501facd62096bf20c5df59ef0dfa Mon Sep 17 00:00:00 2001
From: Keith <165685348+dontslamthedoor@users.noreply.github.com>
Date: Sun, 1 Dec 2024 07:40:51 -0500
Subject: [PATCH] Update ip-address.md

some grammar and punctuation fixes.
---
 website/docs/guide/ip-address.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/docs/guide/ip-address.md b/website/docs/guide/ip-address.md
index 8c2d5edc..18352daa 100644
--- a/website/docs/guide/ip-address.md
+++ b/website/docs/guide/ip-address.md
@@ -6,11 +6,11 @@ sidebar_position: 8
 
 # IP Address
 
-IP address plays fundamental role in HTTP; it's used for access control, auditing, geo-based access analysis and more.
-Echo provides handy method [`Context#RealIP()`](https://godoc.org/github.com/labstack/echo#Context) for that.
+IP address plays a fundamental role in HTTP; it's used for access control, auditing, geo-based access analysis, and more.
+Echo provides a handy method [`Context#RealIP()`](https://godoc.org/github.com/labstack/echo#Context) for that.
 
 However, it is not trivial to retrieve the _real_ IP address from requests especially when you put L7 proxies before the application.
-In such situation, _real_ IP needs to be relayed on HTTP layer from proxies to your app, but you must not trust HTTP headers unconditionally.
+In such situations, _real_ IP needs to be relayed on the HTTP layer from proxies to your app, however, you must not trust HTTP headers unconditionally.
 Otherwise you might give someone a chance of deceiving you. **A security risk!**
 
 To retrieve IP address reliably/securely, you must let your application be aware of the entire architecture of your infrastructrure.