Update clone.md (#3773)

small typo fix: "pre-exisiting relations" to "pre-existing relations"

website/docs/reference/commands/clone.md

@@ -23,7 +23,7 @@ dbt clone --state path/to/artifacts
 # clone one_specific_model of my models from specified state to my target schema(s)
 dbt clone --select one_specific_model --state path/to/artifacts
 
-# clone all of my models from specified state to my target schema(s) and recreate all pre-exisiting relations in the current target
+# clone all of my models from specified state to my target schema(s) and recreate all pre-existing relations in the current target
 dbt clone --state path/to/artifacts --full-refresh
 
 # clone all of my models from specified state to my target schema(s), running up to 50 clone statements in parallel
@@ -36,4 +36,4 @@ Unlike deferral, `dbt clone` requires some compute and creation of additional ob
 
 For example, by creating actual data warehouse objects, `dbt clone` allows you to test out your code changes on downstream dependencies _outside of dbt_ (such as a BI tool). 
 
-As another example, you could `clone` your modified incremental models as the first step of your dbt Cloud CI job to prevent costly `full-refresh` builds for warehouses that support zero-copy cloning.
+As another example, you could `clone` your modified incremental models as the first step of your dbt Cloud CI job to prevent costly `full-refresh` builds for warehouses that support zero-copy cloning.