Skip to content

Commit

Permalink
docs: fix typos
Browse files Browse the repository at this point in the history
  • Loading branch information
jlahovnik committed Aug 20, 2024
1 parent 21daae8 commit 4215f14
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion eodag/plugins/search/data_request_search.py
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ class DataRequestSearch(Search):
* **constraints_file_url** [str]: url to fetch the constraints for a specific product type,
can be an http url or a path to a file; the constraints are used to build queryables
* **constraints_entry** [str]: key in the json result where the constraints can be found;
if not given, it is assumed that the constraints are on tope level of the result, i.e.
if not given, it is assumed that the constraints are on top level of the result, i.e.
the result is an array of constraints
* **metadata_mapping** [Dict[str, Any]]: The search plugins of this kind can detect when a
metadata mapping is "query-able", and get the semantics of how to format the query string
Expand Down
2 changes: 1 addition & 1 deletion eodag/plugins/search/qssearch.py
Original file line number Diff line number Diff line change
Expand Up @@ -265,7 +265,7 @@ class QueryStringSearch(Search):
* **constraints_file_dataset_key** [str]: key which is used in the eodag configuration to
map the eodag product type to the provider product type; default: dataset
* **constraints_entry** [str]: key in the json result where the constraints can be found;
if not given, it is assumed that the constraints are on tope level of the result, i.e.
if not given, it is assumed that the constraints are on top level of the result, i.e.
the result is an array of constraints
* **stop_without_constraints_entry_key** [bool]: if true only a provider result containing
`constraints_entry` is accepted as valid and used to create constraints; default: false
Expand Down

0 comments on commit 4215f14

Please sign in to comment.