diff --git a/bitnami/postgresql-ha/README.md b/bitnami/postgresql-ha/README.md
index e29f45836d7594..6660622b7d3f52 100644
--- a/bitnami/postgresql-ha/README.md
+++ b/bitnami/postgresql-ha/README.md
@@ -33,7 +33,7 @@ There are two different ways to deploy a PostgreSQL cluster, using the PostgreSQ
 
 - Both the PostgreSQL HA and the PostgreSQL chart configures a cluster with a primary/replica topology. The primary node has writing permissions while replication is on the replica nodes which have read-only permissions.
 - The PostgreSQL HA Helm chart deploys a cluster with three nodes by default, one for pgpool, one primary, and one replica for PostgreSQL. The PostgreSQL chart configures a cluster with two nodes by default (one primary and one replica).
-- The PostgreSQL HA Helm chart uses pgpool to handle the connection to the nodes. pgpool is resposible to spread the queries among nodes.
+- The PostgreSQL HA Helm chart uses pgpool to handle the connection to the nodes. pgpool is responsible to spread the queries among nodes.
 - The PostgreSQL HA Helm chart includes a repmgr module that ensures high-availability thanks to automatic membership control. If the primary is down, any of the replica nodes will be promoted as primary to avoid data loss.
 
 The following diagram shows you the options you have for using Bitnami's PostgreSQL solutions in your deployments:
@@ -1284,4 +1284,4 @@ Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
-limitations under the License.
\ No newline at end of file
+limitations under the License.