Skip to content

Commit af5d1a9

Browse files
author
Jesse Farmer
committed
Remove repeated 'every'
1 parent 5a7dfa5 commit af5d1a9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -101,16 +101,16 @@ as if it simply didn't exist.
101101

102102
## Other Solutions to The "Sensitive Information" Problem
103103

104-
In every case, every solution to the "sensitive information" problem follows the
105-
same fundamental pattern:
104+
Every solution to the "sensitive information" problem follows the same
105+
fundamental pattern:
106106

107107
1. Separate your sensitive information from your program
108108
2. Have your program load the file with sensitive information
109109
3. Tell git to ignore that file
110110

111-
That said, dotenv isn't the only solution to this problem. There
112-
are other gems like [figaro](https://github.com/laserlemon/figaro) which do
113-
much the same thing, for example.
111+
That said, dotenv isn't the only solution. There are other gems like
112+
[figaro](https://github.com/laserlemon/figaro) which are very similar to dotenv,
113+
for example.
114114

115115
If you don't want to or can't use a gem to separate sensitive information from
116116
your project, there are a few other options. A common pattern is to create a

0 commit comments

Comments
 (0)