Fix typos and improve grammar (#792)

Author: Simran-B

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.