From 8a41d1292fa5e16e96b20517e943072da0699817 Mon Sep 17 00:00:00 2001 From: Jake Worth Date: Sun, 8 Nov 2015 09:39:01 -0600 Subject: [PATCH] Fix double word 'be' --- src/doc/style/safety/lib-guarantees.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/doc/style/safety/lib-guarantees.md b/src/doc/style/safety/lib-guarantees.md index aa87223383a..8ee64f1806a 100644 --- a/src/doc/style/safety/lib-guarantees.md +++ b/src/doc/style/safety/lib-guarantees.md @@ -70,8 +70,8 @@ that all instances are valid utf-8: Providing library-level guarantees sometimes entails inconvenience (for static checks) or overhead (for dynamic checks). So it is sometimes desirable to allow clients to sidestep this checking, while promising to use the API in a way that -still provides the guarantee. Such escape hatches should only be be introduced -when there is a demonstrated need for them. +still provides the guarantee. Such escape hatches should only be introduced when +there is a demonstrated need for them. It should be trivial for clients to audit their use of the library for escape hatches.