Skip to content

Commit 0818de8

Browse files
committed
some small grammatical corrections
1 parent de9dd65 commit 0818de8

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

draft/faq/storage.txt

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ the :doc:`complete list of FAQs </faq>` or post your question to the
1818
What are memory mapped files?
1919
-----------------------------
2020

21-
Memory mapped files are segments are a way of keeping files and data
21+
Memory mapped files are a way of keeping files and data
2222
up to date in memory using the system call ``mmap()``. MongoDB uses
2323
memory mapped files as its storage engine. By using memory mapped
2424
files MongoDB can treat the content of its data files as if they were
@@ -30,7 +30,7 @@ How do memory mapped files work?
3030

3131
Memory mapping assigns files to a block of virtual memory with a
3232
direct byte-for-byte correlation. Once mapped, the relationship
33-
between file and memory, allows MongoDB to interact with the data in
33+
between file and memory allows MongoDB to interact with the data in
3434
the file as if it were memory.
3535

3636
How does MongoDB work with memory mapped files?
@@ -55,9 +55,9 @@ What is the difference between soft and hard page faults?
5555
---------------------------------------------------------
5656

5757
:term:`Page faults <page fault>` occur when MongoDB needs access to
58-
data that isn't currently in active memory. A "hard" page fault,
58+
data that isn't currently in active memory. A "hard" page fault
5959
refers to situations when MongoDB must access a disk to access the
60-
data. A "soft" page fault, by contrast merely moves memory pages from
60+
data. A "soft" page fault, by contrast, merely moves memory pages from
6161
one list to another, and does not require as much time to complete.
6262

6363
What tools can I use to investigate storage use in MongoDB?
@@ -73,11 +73,11 @@ What is the working set?
7373

7474
Working set represents the total body of data that the application
7575
uses in the course of normal operation. Often this is a subset of the
76-
total data size, but the specific size of working set depends on
76+
total data size, but the specific size of the working set depends on
7777
actual moment-to-moment use of the database.
7878

7979
If you run a query that requires MongoDB to scan every
80-
:term:`document` in a collection, the working set includes every
80+
:term:`document` in a collection, the working set includes every active
8181
document in memory.
8282

8383
For best performance, the majority of your *active* set should fit in

0 commit comments

Comments
 (0)