Minor Changes

content/en/docs/guides/contributor-guides/helm-to-operator-codegen-sdk-developer-guide.md

@@ -17,7 +17,7 @@ After the conversion process, all the generated Go code is gathered and compiled
 -----
 ### Flow-1: Helm to YAML
 Helm to YAML conversion is achieved by running the following command
-`helm template <chart>  --namespace <namespace>  --output-dir “temp/templated/”` Internally. As of now, it retrieves the values from default "values.yaml"
+`helm template <chart>  --namespace <namespace>  --output-dir “temp/templated/”` internally. As of now, it retrieves the values from default "values.yaml"
 
 ### Flow-2: YAML Split
 The SDK iterates over each YAML file in the "converted-yamls" directory. If a YAML file contains multiple Kubernetes Resource Models (KRM), separated by "---", the SDK splits the YAML file accordingly to isolate each individual KRM resource. This ensures that each KRM resource is processed independently.

content/en/docs/guides/user-guides/helm/helm-to-operator-codegen-sdk-user-guide.md

@@ -9,7 +9,7 @@ The [Helm to Operator Codegen SDK](https://github.com/nephio-project/nephio-sdk/
 
 By utilizing the Helm to Operator Codegen SDK, users can efficiently convert existing Helm charts into Kubernetes operators. This transition enables users to leverage the advanced capabilities provided by Kubernetes operators, such as enhanced automation, lifecycle management, and custom logic handling. Overall, the SDK facilitates a smooth migration process, empowering users to embrace the operator model for managing their Kubernetes resources effectively.
 
-## Excercise: Deploying Free5gc using operator
+## Exercise: Deploying Free5gc using operator
 In the following exercise, the objective is to convert the Free5gc Helm chart to Go code suitable for a Kubernetes operator using the sdk. Once the conversion is complete, the generated Go code will be used to deploy all the resources defined in the Free5gc Helm chart using a Kubernetes operator.
 
 ### Step 0: Prerequisite