Update docs/content/en/docs/documentation/dependent-resource-and-workflows/dependent-resources.md

Co-authored-by: Martin Stefanko <xstefank122@gmail.com>

Author: csviri

docs/content/en/docs/documentation/dependent-resource-and-workflows/dependent-resources.md

@@ -306,7 +306,7 @@ it is always possible to override this automated discrimination using several me
 - Override the [`targetSecondaryResourceID`](https://github.com/operator-framework/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/kubernetes/KubernetesDependentResource.java#L282)
   method, if your `DependentResource` extends `KubernetesDependentResource`,
   where it's very often possible to easily determine the `ResourceID` of the secondary resource. This would probably be
-  the easiest solution if you're working with Kubernetes resources. Similarly, for you can override the 
+  the easiest solution if you're working with Kubernetes resources. Similarly, you can override the 
   [`targetSecondaryResourceID`](https://github.com/operator-framework/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/AbstractExternalDependentResource.java#L138)
   for external resources. See below the related ID handling
 - If the approach from above doesn't fit your needs, you can override the target resource selection mechanism by overriding