Fix typos (#1319)

Author: deining

pages/advanced-algorithms/available-algorithms/biconnected_components.mdx

@@ -95,7 +95,7 @@ MERGE (a:Node {id: 8}) MERGE (b:Node {id: 9}) CREATE (a)-[:RELATION]->(b);
 MERGE (a:Node {id: 10}) MERGE (b:Node {id: 11}) CREATE (a)-[:RELATION]->(b);
 ```
 
-{<h3 className="custom-header"> Find biconnected componentes </h3>} 
+{<h3 className="custom-header"> Find biconnected components </h3>} 
 
 Get the values using the following query:
 

pages/advanced-algorithms/available-algorithms/elasticsearch_synchronization.mdx

@@ -142,10 +142,10 @@ If subgraph is not specified, the algorithm is computed on the entire graph by d
 - `edge_index: string` -> The name of the **edge index**. Can be used for both **streaming and parallel bulk**.
 - `thread_count: int` -> **Size of the threadpool** to use for the bulk requests.
 - `chunk_size: int (default=500)` -> The number of docs sent to Elasticsearch in one chunk.
-- `max_chunk_bytes: int (default=104857600)` -> The maximum size of the request in bytes. The default equalls to 100 MB.
+- `max_chunk_bytes: int (default=104857600)` -> The maximum size of the request in bytes. The default equals to 100 MB.
 - `raise_on_error: bool (default=True)` -> Raise `BulkIndexError` containing errors (as .errors) from the execution of the last chunk when some occur.
 - `raise_on_exception: bool` -> If `False` then don’t propagate exceptions from call to bulk and just report the items that failed as failed.
-- `max_retries: int (default=0)` -> Maximum number of times a document will be retried when a 429 is received. The 0 equalls to no retries on 429.
+- `max_retries: int (default=0)` -> Maximum number of times a document will be retried when a 429 is received. The 0 equals to no retries on 429.
 - `initial_backoff: float` -> The number of seconds Elasticsearch should wait before the first retry. Any subsequent retries will be powers of `initial_backoff * 2**retry_number`
 - `max_backoff: float` -> The maximum number of seconds a retry will wait.
 - `yield_ok: float` -> If set to `False` will skip successful documents in the output.
@@ -182,10 +182,10 @@ If subgraph is not specified, the algorithm is computed on the entire graph by d
 - `edge_index: string` -> The name of the **edge index**. Can be used for both **streaming and parallel bulk**.
 - `thread_count: int` -> **Size of the threadpool** to use for the bulk requests.
 - `chunk_size: int (default=500)` -> The number of docs sent to Elasticsearch in one chunk.
-- `max_chunk_bytes: int (default=104857600)` -> The maximum size of the request in bytes. The default equalls to 100 MB.
+- `max_chunk_bytes: int (default=104857600)` -> The maximum size of the request in bytes. The default equals to 100 MB.
 - `raise_on_error: bool (default=True)` -> Raise `BulkIndexError` containing errors (as .errors) from the execution of the last chunk when some occur.
 - `raise_on_exception: bool` -> If `False` then don’t propagate exceptions from call to bulk and just report the items that failed as failed.
-- `max_retries: int (default=0)` -> Maximum number of times a document will be retried when a 429 is received. The 0 equalls to no retries on 429.
+- `max_retries: int (default=0)` -> Maximum number of times a document will be retried when a 429 is received. The 0 equals to no retries on 429.
 - `initial_backoff: float` -> The number of seconds Elastichsearch should wait before the first retry. Any subsequent retries will be powers of `initial_backoff * 2**retry_number`
 - `max_backoff: float` -> The maximum number of seconds a retry will wait.
 - `yield_ok: float` -> If set to `False` will skip successful documents in the output.

pages/advanced-algorithms/available-algorithms/gnn_link_prediction.mdx

@@ -145,7 +145,7 @@ networks** to compute **node embeddings**.
 
 All other parameters are optional.
 
-When setting the model paramaters, if you specify the `split_ratio 1.0`, the
+When setting the model parameters, if you specify the `split_ratio 1.0`, the
 model will train normally on a whole dataset without validating its performance
 on a validation set. However, if the `split_ratio` is a value between 0.0 and
 1.0 but the graph is too small to have such a split, an exception will be

pages/advanced-algorithms/available-algorithms/igraphalg.mdx

@@ -326,7 +326,7 @@ If subgraph is not specified, the algorithm is computed on the entire graph by d
 
 {<h4 className="custom-header"> Usage: </h4>}
 
-Use the following query to find the community strucutre:
+Use the following query to find the community structure:
 
 ```cypher
     CALL igraphalg.community_leiden() 

pages/advanced-algorithms/available-algorithms/node2vec_online.mdx

@@ -176,7 +176,7 @@ RETURN message;
 
 ### `update()`
 
-Use the `udpate()` procedure to (re)calculate embeddings.
+Use the `update()` procedure to (re)calculate embeddings.
 
 {<h4 className="custom-header"> Input: </h4>}
 
@@ -297,7 +297,7 @@ MERGE (n:Node {id: 8}) MERGE (m:Node {id: 4}) CREATE (n)-[:RELATION]->(m);
 MERGE (n:Node {id: 4}) MERGE (m:Node {id: 6}) CREATE (n)-[:RELATION]->(m);
 ```
 
-{<h3 className="custom-header"> Set the paramaters </h3>} 
+{<h3 className="custom-header"> Set the parameters </h3>} 
 
 To set the parameters for the updater and the learner, use the following query:
 

pages/advanced-algorithms/available-algorithms/nxalg.mdx

@@ -82,7 +82,7 @@ If subgraph is not specified, the algorithm is computed on the entire graph by d
 
 {<h4 className="custom-header"> Output: </h4>}
 
-- `paths: List[Vertex]` ➡ List of ndoes for a certain path.
+- `paths: List[Vertex]` ➡ List of nodes for a certain path.
 
 {<h4 className="custom-header"> Usage: </h4>}
 
@@ -2379,7 +2379,7 @@ If subgraph is not specified, the algorithm is computed on the entire graph by d
 
 {<h4 className="custom-header"> Usage: </h4>}
 
-To get nodes in a stronly connected components, run the following query:
+To get nodes in strongly connected components, run the following query:
 
 ```cypher
 CALL nxalg.strongly_connected_components() 

pages/advanced-algorithms/available-algorithms/tgn.mdx

@@ -334,7 +334,7 @@ If subgraph is not specified, the algorithm is computed on the entire graph by d
 
 {<h4 className="custom-header"> Usage: </h4>}
 
-To get resuts, use the following query:
+To get results, use the following query:
 
 ```cypher
 CALL tgn.get_results() 

pages/advanced-algorithms/available-algorithms/weakly_connected_components.mdx

@@ -42,7 +42,7 @@ You can execute this algorithm on [graph projections, subgraphs or portions of t
 
 ### `get()`
 
-Use the procedure to get disconnected componentes.
+Use the procedure to get disconnected components.
 
 {<h4 className="custom-header"> Input: </h4>}
 

pages/advanced-algorithms/available-algorithms/xml_module.mdx

@@ -334,7 +334,7 @@ If the XPath expression is not empty, the output is all elements that satisfy th
 
 {<h4 className="custom-header"> Usage: </h4>}
 
-This section shows the usage of the procedure on the folllowing [**XML
+This section shows the usage of the procedure on the following [**XML
 file**](https://www.w3schools.com/xml/note.xml)
 
 **Parse an XML file from URL**

pages/ai-ecosystem/integrations.mdx

@@ -218,7 +218,7 @@ paths and in LlamaIndex, several node retrieval methods at once can be combined.
 If no sub-retrievers are provided, the defaults are
 [LLMSynonymRetriever](https://docs.llamaindex.ai/en/latest/module_guides/indexing/lpg_index_guide/#default-llmsynonymretriever)
 and
-[VectorContexRetriever](https://docs.llamaindex.ai/en/latest/module_guides/indexing/lpg_index_guide/#default-if-supported-vectorcontextretriever),
+[VectorContextRetriever](https://docs.llamaindex.ai/en/latest/module_guides/indexing/lpg_index_guide/#default-if-supported-vectorcontextretriever),
 if supported.
 
 From the latest update, LlamaIndex utilizes Memgraph's **[vector search](/querying/vector-search)** feature in
@@ -315,7 +315,7 @@ pip install langchain langchain-openai langchain-memgraph langgraph
 Don't forget to install `langgraph`, as it is a prerequisite to use Memgraph
 toolkit.
 
-{<h4 className="custom-header">Enviroment setup </h4>}
+{<h4 className="custom-header">Environment setup </h4>}
 
 Make sure you have [Memgraph](/getting-started) running
 in the background.