From 58b4eb908983465fca6317bef9e8eea923465ee0 Mon Sep 17 00:00:00 2001 From: Andrea Gelmini Date: Sat, 6 Mar 2021 23:38:33 +0100 Subject: [PATCH] Fix typo --- README.md | 2 +- man/mergerfs.1 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1bf2ed31..526116af 100644 --- a/README.md +++ b/README.md @@ -1165,7 +1165,7 @@ If `mergerfs` doesn't work as a type it could be due to how the `mount.mergerfs` See above first. -If/when mergerfs is rewritten to use the low-level API then it'll be plausible to support system libfuse but till then its simply too much work to manage the differences across the versions. +If/when mergerfs is rewritten to use the low-level API then it'll be plausible to support system libfuse but till then it's simply too much work to manage the differences across the versions. #### Why use mergerfs over mhddfs? diff --git a/man/mergerfs.1 b/man/mergerfs.1 index d46ce056..33c7ae89 100644 --- a/man/mergerfs.1 +++ b/man/mergerfs.1 @@ -2504,7 +2504,7 @@ Longer term the plan is to rewrite mergerfs to use the low level API. See above first. .PP If/when mergerfs is rewritten to use the low\-level API then it\[aq]ll -be plausible to support system libfuse but till then its simply too much +be plausible to support system libfuse but till then it's simply too much work to manage the differences across the versions. .SS Why use mergerfs over mhddfs? .PP