Fixing missing chars :-(

Ch16/Ch16.md

@@ -465,7 +465,7 @@ asking RavenDB what's going on directly. In the RavenDB Studio, go to your datab
 The tree map in Figure 16.8 should help you figure out at a glance what's taking up space in your
 database. Below the tree map, you'll see a table similar to our Table 16.3.
 
-|   Type    |           Name            | Size (∑ 800.62 MB) | % Total |
+|   Type    |           Name            | Size (SUM 800.62 MB) | % Total |
 |-----------|---------------------------|--------------------|---------|
 | Documents | blog.ayende.com           | 320 MB             | 39.97%  |
 | Index     | PostComments/CreationDate | 96 MB              | 11.99%  |
@@ -495,7 +495,7 @@ makes sure that the file system allocation is otherwise unchanged.
 
 Going back to the tree map, you can click on the `Datafile` entry to see the breakdown inside the actual database. Table 16.4 shows what this looks like for a blog database.
 
-|   Type   |         Name          |    Size (∑ 256 MB)    | % Total |
+|   Type   |         Name          |    Size (SUM 256 MB)    | % Total |
 |----------|-----------------------|-----------------------|---------|
 | Tables   | Tables                | 156.22 MB             | 61.03%  |
 | Free     | Free                  | 93.70 MB              | 36.60%  |
@@ -511,7 +511,7 @@ A table in this context is not a relational table, but rather an internal struct
 storage engine. This is how RavenDB stores data internally. You can click `Tables` to see more about how much space
 is used by each one, as shown in Table 16.5.
 
-| Type  |                Name                | Entries | Size (∑ 156.22 MB) | % Total |
+| Type  |                Name                | Entries | Size (SUM 156.22 MB) | % Total |
 |-------|------------------------------------|---------|--------------------|---------|
 | Table | Collection.Documents.postcomments  |   6,604 | 50.65 MB           | 32.42%  |
 | Table | Collection.Documents.posts         |   6,589 | 40.21 MB           | 25.74%  |