angri avatar angri committed 994c7c3

[docs] some small fixes in "limits" section

Comments (0)

Files changed (1)

     Therefore the limit of number of trees is defined by the highest
     integer for DBMS in use. This is not configurable. If you expect
     to have more than 2**31 trees you might want to use custom field
-    for tree id with a different numeric type (supposedly ``BIGINT``)
-    and probably set up an index on it to speed up creating new trees.
+    for tree id with a different numeric type (supposedly ``BIGINT``).
 *Number of children in each node:*
     Imposed by the length of one path segment. Can be configured
     using the "steplen" parameter (see :class:`MPManager`). The number
     would limit your tree to 1679616 maximum children and 2561 maximum
     depth.
 *Total number of nodes in a tree:*
-    There is no such limit. Not any that you can hit even (with extremely
+    There is no such limit. Not any that you can hit even with (extremely
     low) default path length. The total number of nodes in a tree
     is equal to "36 ** pathlen" and with "pathlen=255" it is something
     around ``7.2e+397``.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.