From 94b97a0affdfb41ddb357dd488fcb020f87c54e1 Mon Sep 17 00:00:00 2001 From: Alex Flinn Date: Tue, 20 Nov 2018 18:56:33 +0000 Subject: [PATCH] Update nfs_host_client_setup.md typo correction --- doc/administration/high_availability/nfs_host_client_setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/administration/high_availability/nfs_host_client_setup.md b/doc/administration/high_availability/nfs_host_client_setup.md index 00b5700373235b..164e004d5a4564 100644 --- a/doc/administration/high_availability/nfs_host_client_setup.md +++ b/doc/administration/high_availability/nfs_host_client_setup.md @@ -6,7 +6,7 @@ setup act as clients while the NFS server plays host. > Note: The instructions provided in this documentation allow for setting a quick proof of concept but will leave NFS as potential single point of failure and -therefore not recommended for use in porduction. Explore options such as [Pacemaker +therefore not recommended for use in production. Explore options such as [Pacemaker and Corosync](http://clusterlabs.org/) for highly available NFS in production. Below are instructions for setting up an application node(client) in an HA cluster -- GitLab