Fix typos and improve grammar

site/content/3.12/about-arangodb/_index.md

@@ -21,7 +21,7 @@ cloud service, the [ArangoGraph Insights Platform](../arangograph/_index.md).
 
 ## What are Graphs?
 
-Graphs are information networks comprised of nodes and edges.
+Graphs are information networks composed of nodes and edges.
 
 ![An arrow labeled as "Edge" pointing from one circle to another, both labeled "Node"](../../images/data-model-graph-relation-abstract-edge.png)
 

site/content/3.12/aql/execution-and-performance/query-profiling.md

@@ -6,7 +6,7 @@ description: >-
   For understanding the performance of specific queries, you can profile them to
   identify slow parts of query execution plans
 ---
-ArangoDB allows to execute your query with special instrumentation code enabled.
+ArangoDB allows you to execute your query with special instrumentation code enabled.
 It provides you a query plan with detailed execution statistics.
 
 To use this in an interactive fashion on the shell you can use

site/content/3.12/aql/functions/date.md

@@ -9,12 +9,12 @@ description: >-
 ## Date and time representations
 
 AQL offers functionality to work with dates, but it does not have a special data type
-for dates (neither does JSON, which is usually used as format to ship data into and
+for dates (neither does JSON, which is usually used as a format to ship data into and
 out of ArangoDB). Instead, dates in AQL are represented by either numbers or strings.
 
 All date function operations are done in the *Unix time* system. Unix time counts
-all non leap seconds beginning with January 1st 1970 00:00:00.000 UTC, also know as
-the Unix epoch. A point in time is called timestamp. A timestamp has the same value
+all non leap seconds beginning with January 1st 1970 00:00:00.000 UTC, also known as
+the Unix epoch. A point in time is called a timestamp. A timestamp has the same value
 at every point on earth. The date functions use millisecond precision for timestamps.
 
 Time unit definitions:
@@ -148,7 +148,7 @@ The date time string always uses UTC / Zulu time, indicated by the `Z` at its en
 
 `DATE_ISO8601(year, month, day, hour, minute, second, millisecond) → dateString`
 
-Return a ISO 8601 date time string from `date`, but allows to specify the individual
+Return an ISO 8601 date time string from `date`, but allows you to specify the individual
 date components separately. All parameters after `day` are optional.
 
 - **year** (number): typically in the range 0..9999, e.g. `2017`
@@ -174,7 +174,7 @@ To convert the return value to seconds, divide it by 1000.
 
 `DATE_TIMESTAMP(year, month, day, hour, minute, second, millisecond) → timestamp`
 
-Create a timestamp value, but allows to specify the individual date components
+Create a timestamp value, but allows you to specify the individual date components
 separately. All parameters after `day` are optional.
 
 - **year** (number): typically in the range 0..9999, e.g. `2017`
@@ -779,7 +779,7 @@ RETURN DATE_DAYS_IN_MONTH("2020-02-01")
 ---
 name: datedysmn4
 description: |
-  Determine the number of days in February in a a non-leap year using a date time string:
+  Determine the number of days in February in a non-leap year using a date time string:
 ---
 RETURN DATE_DAYS_IN_MONTH("2021-02-01")
 ```

site/content/3.12/aql/functions/numeric.md

@@ -261,10 +261,10 @@ DEGREES(3.141592653589793) // 180
 
 `EXP(value) → num`
 
-Return Euler's constant (2.71828...) raised to the power of *value*.
+Return Euler's constant (2.71828...) raised to the power of the *value*.
 
 - **value** (number): the input value
-- returns **num** (number): Euler's constant raised to the power of *value*
+- returns **num** (number): Euler's constant raised to the power of the *value*
 
 ```aql
 EXP(1) // 2.718281828459045
@@ -276,10 +276,10 @@ EXP(0) // 1
 
 `EXP2(value) → num`
 
-Return 2 raised to the power of *value*.
+Return 2 raised to the power of the *value*.
 
 - **value** (number): the input value
-- returns **num** (number): 2 raised to the power of *value*
+- returns **num** (number): 2 raised to the power of the *value*
 
 ```aql
 EXP2(16) // 65536

site/content/3.12/aql/graphs/shortest-path.md

@@ -142,7 +142,7 @@ FOR node IN OUTBOUND SHORTEST_PATH
 ```
 
 All collections in the list that do not specify their own direction use the
-direction defined after `IN` (here: `OUTBOUND`). This allows to use a different
+direction defined after `IN` (here: `OUTBOUND`). This allows you to use a different
 direction for each collection in your path search.
 
 ## Conditional shortest path

site/content/3.12/aql/graphs/traversals.md

@@ -331,7 +331,7 @@ FOR node IN OUTBOUND
 ```
 
 All collections in the list that do not specify their own direction use the
-direction defined after `IN`. This allows to use a different direction for each
+direction defined after `IN`. This allows you to use a different direction for each
 collection in your traversal.
 
 ### Graph traversals in a cluster
@@ -542,7 +542,7 @@ string, for instance, which evaluates to `true` for the `null` value.
 The depth at which a traversal is stopped by pruning is considered as a result,
 but in the above example, the minimum depth of `2` filters the start node out.
 If you lower the minimum depth to `0`, you get **London** as the sole result.
-This confirms that the traversal stopped at the start vertex.
+This confirms that the traversal stopped at the start node.
 
 To avoid this problem, exclude the `null` value. For example, you can use
 `e.travelTime > 0 AND e.travelTime < 2.5`, but more generic solutions are to

site/content/3.12/arangograph/my-account.md

@@ -47,7 +47,7 @@ accessible from every view. There are two elements:
 1. Hover over or click the user icon of the __User Toolbar__ in the top right corner.
 2. Click __My organizations__ in the __My account__ section.
 3. Click the __New organization__ button.
-4. Enter a name and and a description for the new organization and click the
+4. Enter a name and a description for the new organization and click the
    __Create__ button.
 
 {{< info >}}

site/content/3.12/components/tools/arangoimport/examples-json.md

@@ -258,7 +258,7 @@ arangoimport --threads 4 --file "data.jsonl" --type jsonl --collection users
 Using multiple threads may lead to a non-sequential import of the input
 data. Data that appears later in the input file may be imported earlier than data
 that appears earlier in the input file. This is normally not a problem but may cause
-issues when when there are data dependencies or duplicates in the import data. In
+issues when there are data dependencies or duplicates in the import data. In
 this case, the number of threads should be set to 1. Also, using parallelism with
 the `--threads X` parameter together with the `--on-duplicate` parameter set to `ignore`,
 `update` or `replace` can lead to a race condition, when there are duplicates e.g. multiple 

site/content/3.12/concepts/data-models.md

@@ -41,7 +41,7 @@ values, and more.
 
 ## Graph Model
 
-Graphs are comprised of **nodes** and **edges**. Both are documents in
+Graphs are composed of **nodes** and **edges**. Both are documents in
 ArangoDB. Edges have two special attributes, `_from` and `_to`, that reference
 the source and target nodes by their document identifiers.
 

site/content/3.12/data-science/integrations/_index.md

@@ -9,7 +9,7 @@ aliases:
   - adapters
 ---
 ArangoDB Adapters provide a convenient way to integrate ArangoDB with popular
-data science tools. By enabling you to to use your preferred programming
+data science tools. By enabling you to use your preferred programming
 languages and libraries, these adapters simplify the data analysis
 process and make it easier to leverage the power of ArangoDB in data science.
 

site/content/3.12/data-science/integrations/arangodb-rdf-adapter.md

@@ -143,7 +143,7 @@ to append the prefix and form the full URI as a property.
 #### Identifiers
 
 URIs (e.g `http://dbpedia.org/resource/`) are used as universal identifiers in 
-RDF but contain contain special characters, namely `:` and `/`, which make them not 
+RDF but contain special characters, namely `:` and `/`, which make them not 
 suitable for use as an ArangoDB `_key` attribute. Consequently, a hashing algorithm
 is used within ArangoRDF to store the URI as an ArangoDB graph node.
 

site/content/3.12/deploy/architecture/data-sharding.md

@@ -6,7 +6,7 @@ description: >-
   ArangoDB can divide collections into multiple shards to distribute the data
   across multiple cluster nodes
 ---
-ArangoDB organizes its collection data in _shards_. Sharding allows to use
+ArangoDB organizes its collection data in _shards_. Sharding allows you to use
 multiple machines to run a cluster of ArangoDB instances that together
 constitute a single database system.
 
@@ -28,7 +28,7 @@ There are two main ways of scaling a database system:
 - Vertical scaling
 - Horizontal scaling
 
-Vertical scaling scaling means to upgrade to better server hardware (faster
+Vertical scaling means to upgrade to better server hardware (faster
 CPU, more RAM / disk). This can be a cost effective way of scaling, because
 administration is easy and performance characteristics do not change much.
 Reasoning about the behavior of a single machine is also a lot easier than

site/content/3.12/deploy/cluster/_index.md

@@ -3,7 +3,7 @@ title: Cluster deployments
 menuTitle: Cluster
 weight: 15
 description: >-
-  ArangoDB clusters are comprised of DB-Servers, Coordinators, and Agents, with
+  ArangoDB clusters are composed of DB-Servers, Coordinators, and Agents, with
   synchronous data replication between DB-Servers and automatic failover
 ---
 The Cluster architecture of ArangoDB is a _CP_ master/master model with no
@@ -130,7 +130,7 @@ all the machines participating to the Cluster.
 
 Using the roles outlined above an ArangoDB Cluster is able to distribute
 data in so called _shards_ across multiple _DB-Servers_. Sharding
-allows to use multiple machines to run a cluster of ArangoDB
+allows you to use multiple machines to run a cluster of ArangoDB
 instances that together constitute a single database. This enables
 you to store much more data, since ArangoDB distributes the data
 automatically to the different servers. In many situations one can
@@ -196,7 +196,7 @@ are always sent to the _DB-Server_ which happens to hold the _leader_ copy,
 which in turn replicates the changes to all _followers_ before the operation
 is considered to be done and reported back to the _Coordinator_.
 Internally, read operations are all served by the _DB-Server_ holding the _leader_ copy,
-this allows to provide snapshot semantics for complex transactions.
+this allows you to provide snapshot semantics for complex transactions.
 
 Using synchronous replication alone guarantees consistency and high availability
 at the cost of reduced performance: write requests have a higher latency
@@ -278,7 +278,7 @@ now contact a different _DB-Server_ for requests to this _shard_. Service
 resumes. The other surviving _replicas_ automatically resynchronize their
 data with the new _leader_. 
 
-In addition to the above, one of the following two cases cases can happen:
+In addition to the above, one of the following two cases can happen:
 
 - **A**: If another _DB-Server_ (that does not hold a _replica_ for this _shard_ already)
   is available in the Cluster, a new _follower_ is automatically
@@ -339,11 +339,11 @@ with a timeout error.
 ## Shard movement and resynchronization
 
 All _shard_ data synchronizations are done in an incremental way, such that
-resynchronizations are quick. This technology allows to move shards
+resynchronizations are quick. This technology allows you to move shards
 (_follower_ and _leader_ ones) between _DB-Servers_ without service interruptions.
 Therefore, an ArangoDB Cluster can move all the data on a specific _DB-Server_
 to other _DB-Servers_ and then shut down that server in a controlled way.
-This allows to scale down an ArangoDB Cluster without service interruption,
+This allows you to scale down an ArangoDB Cluster without service interruption,
 loss of fault tolerance or data loss. Furthermore, one can re-balance the
 distribution of the _shards_, either manually or automatically.
 

site/content/3.12/develop/exit-codes.md

@@ -14,7 +14,7 @@ Exit codes are numeric values programs return when they finish, indicating
 success or failure.
 
 - An exit code of zero indicates a successful execution, e.g. the termination of
-  the server process without without any issues.
+  the server process without any issues.
 - Any non-zero exit code indicates that some error occurred, e.g. you tried to
   run a program with invalid parameters or it failed to process something.
 

site/content/3.12/develop/foxx-microservices/reference/configuration.md

@@ -43,7 +43,7 @@ The parameter definition can have the following properties:
     any well-formed JSON value.
 
   - `"password"`:
-    like *string* but will be displayed as a masked input field in the web web interface.
+    like *string* but will be displayed as a masked input field in the web interface.
 
 - **default**: `any`
 

site/content/3.12/develop/http-api/general-request-handling.md

@@ -215,7 +215,7 @@ non-queued request.
 The following should be noted about how ArangoDB handles client errors in its
 HTTP layer:
 
-- client requests using an HTTP version signature different than `HTTP/1.0` or
+- client requests using an HTTP version signature different from `HTTP/1.0` or
   `HTTP/1.1` will get an **HTTP 505** (HTTP Version Not Supported) error in return.
 - ArangoDB will reject client requests with a negative value in the
   `Content-Length` request header by closing the connection.

site/content/3.12/develop/http-api/queries/aql-queries.md

@@ -3107,7 +3107,7 @@ paths:
                     maxNumberOfPlans:
                       description: |
                         The maximum number of plans that the optimizer is allowed to
-                        generate. Setting this attribute to a low value allows to put a
+                        generate. Setting this attribute to a low value allows you to put a
                         cap on the amount of work the optimizer does.
 
                         Default: Controlled by the `--query.optimizer-max-plans` startup option.

site/content/3.12/develop/http-api/queries/aql-query-results-cache.md

@@ -58,7 +58,7 @@ paths:
                   properties:
                     hash:
                       description: |
-                        The hash value calculated from the the query string,
+                        The hash value calculated from the query string,
                         certain query options, and the bind variables.
                       type: string
                     query:

site/content/3.12/develop/http-api/views/arangosearch-views.md

@@ -200,7 +200,7 @@ paths:
                       ```
 
                     The `storedValues` option is not to be confused with the `storeValues` option,
-                    which allows to store meta data about attribute values in the View index.
+                    which allows you to store meta data about attribute values in the View index.
                   type: array
                   default: []
                   items:

site/content/3.12/develop/integrations/spring-data-arangodb/reference-version-3/repositories/queries/named-queries.md

@@ -33,7 +33,7 @@ The corresponding `arango-named-queries.properties` file looks like this:
 Customer.findByUsername = FOR c IN customers FILTER c.username == @username RETURN c
 ```
 
-The queries specified in the properties file are no different than the queries
+The queries specified in the properties file are no different from the queries
 that can be defined with the `@Query` annotation. The only difference is that
 the queries are in one place. If there is a `@Query` annotation present and a
 named query defined, the query in the `@Query` annotation takes precedence.

site/content/3.12/develop/integrations/spring-data-arangodb/reference-version-4/repositories/queries/named-queries.md

@@ -28,7 +28,7 @@ The corresponding `arango-named-queries.properties` file looks like this:
 Customer.findByUsername = FOR c IN customers FILTER c.username == @username RETURN c
 ```
 
-The queries specified in the properties file are no different than the queries
+The queries specified in the properties file are no different from the queries
 that can be defined with the `@Query` annotation. The only difference is that
 the queries are in one place. If there is a `@Query` annotation present and a
 named query defined, the query in the `@Query` annotation takes precedence.

site/content/3.12/develop/transactions/javascript-transactions.md

@@ -307,7 +307,7 @@ For a complete list of possible ArangoDB errors, see
 ### Custom Exceptions
 
 You may want to define custom exceptions inside of a transaction. To have the
-exception propagate upwards properly, please throw an an instance of base
+exception propagate upwards properly, please throw an instance of the base
 JavaScript `Error` class or a derivative. To specify an error number, include it
 as the `errorNumber` field. As an example:
 

site/content/3.12/develop/transactions/locking-and-isolation.md

@@ -48,7 +48,7 @@ be a write-write conflict, and one of the transactions will abort with error 120
 accept the failure.
 
 In order to guard long-running or complex transactions against concurrent operations
-on the same data, the RocksDB engine allows to access collections in exclusive mode.
+on the same data, the RocksDB engine allows you to access collections in exclusive mode.
 Exclusive accesses will internally acquire a write-lock on the collections, so they 
 are not executed in parallel with any other write operations. Read operations can still
 be carried out by other concurrent transactions.
@@ -208,7 +208,7 @@ db._executeTransaction({
 
 In the above example, a deadlock will occur if transaction T1 and T2 have both
 acquired their write locks (T1 for collection `c1` and T2 for collection `c2`) and
-are then trying to read from the other other (T1 will read from `c2`, T2 will read
+are then trying to read from the other (T1 will read from `c2`, T2 will read
 from `c1`). T1 will then try to acquire the read lock on collection `c2`, which
 is prevented by transaction T2. T2 however will wait for the read lock on 
 collection `c1`, which is prevented by transaction T1. 

site/content/3.12/get-started/_index.md

@@ -49,7 +49,7 @@ MariaDB or PostgreSQL, you should be familiar with the SQL query language.
 ArangoDB's query language is called AQL. There are some similarities between both
 languages despite the different data models of the database systems. The most
 notable difference is probably the concept of loops in AQL, which makes it feel
-more like a programming language. It suits the schema-less model more natural
+more like a programming language. It suits the schema-less model more naturally
 and makes the query language very powerful while remaining easy to read and write.
 
 To get started with AQL, sign up for [ArangoDB University](https://university.arangodb.com/)

site/content/3.12/get-started/on-premises-installation.md

@@ -66,7 +66,7 @@ See [Securing Starter Deployments](../operations/security/securing-starter-deplo
 <!-- NOT ON-PREMISES SPECIFIC!
 Authentication
 
-ArangoDB allows to restrict access to databases to certain users. All
+ArangoDB allows you to restrict access to databases to certain users. All
 users of the system database are considered administrators. During
 installation a default user *root* is created, which has access to
 all databases.

site/content/3.12/get-started/start-using-aql/crud.md

@@ -36,7 +36,7 @@ INSERT {
 ```
 
 The syntax is `INSERT document INTO collectionName`. The document is an object
-like you may know it from JavaScript or JSON, which is comprised of attribute
+like you may know it from JavaScript or JSON, which is composed of attribute
 key and value pairs. The quotes around the attribute keys are optional in AQL.
 Keys are always character sequences (strings), whereas attribute values can
 have [different types](../../aql/fundamentals/data-types.md):
@@ -223,7 +223,7 @@ RETURN DOCUMENT("Characters/ned")
 ]
 ```
 
-The `DOCUMENT()` function also allows to fetch multiple documents at once:
+The `DOCUMENT()` function also allows you to fetch multiple documents at once:
 
 ```aql
 RETURN DOCUMENT("Characters", ["ned", "catelyn"])

site/content/3.12/graphs/_index.md

@@ -10,7 +10,7 @@ description: >-
 aliases:
   - graphs/first-steps
 ---
-Graphs are information networks comprised of **nodes** and **edges**. Nodes
+Graphs are information networks composed of **nodes** and **edges**. Nodes
 can represent objects, entities, abstract concepts, or ideas. edges between
 nodes can represent relations like physical and social connections, temporal and
 causal relationships, flows of information, energy, and material, interactions and

site/content/3.12/graphs/graph-analytics.md

@@ -420,7 +420,7 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d '{"database":"_system","gra
 PageRank is a well known algorithm to rank nodes in a graph: the more
 important a node, the higher rank it gets. It goes back to L. Page and S. Brin's
 [paper](http://infolab.stanford.edu/pub/papers/google.pdf) and
-is used to rank pages in in search engines (hence the name). The algorithm runs
+is used to rank pages in search engines (hence the name). The algorithm runs
 until the execution converges. To run for a fixed number of iterations, use the
 `maximum_supersteps` parameter.