Fixed some grammatical mistakes (#9456)

* Grammatical_error in docs/api_reference/query.rst

* Grammatical error in docs/end_to_end_tutorials/dev_practices/e2e_evaluation.md

---------

Co-authored-by: KamalSharmaShorthillsAI <kamal@shorthills.ai>
Co-authored-by: Haotian Zhang <socool.king@gmail.com>

docs/api_reference/query.rst

@@ -9,7 +9,7 @@ This doc shows the classes that are used to query indices.
 Main Query Classes
 ^^^^^^^^^^^^^^^^^^
 
-Querying an index involves a three main components:
+Querying an index involves three main components:
 
 - **Retrievers**: A retriever class retrieves a set of Nodes from an index given a query.
 - **Response Synthesizer**: This class takes in a set of Nodes and synthesizes an answer given a query.

docs/optimizing/evaluation/e2e_evaluation.md

@@ -58,7 +58,7 @@ It may be expensive to use GPT-4 to carry out evaluation especially as your dev
 
 Metrics ensembling uses an ensemble of weaker signals (exact match, F1, ROUGE, BLEU, BERT-NLI and BERT-similarity) to predict the output of a more expensive evaluation methods that are closer to the gold labels (human-labelled/GPT-4).
 
-It is intenteded for two purposes:
+It is intended for two purposes:
 
 1. Evaluating changes cheaply and quickly across a large dataset during the development stage.
 2. Flagging outliers for further evaluation (GPT-4 / human alerting) during the production monitoring stage.