fix typos in starship

Author: Anmol1696

clients/go/client/config.go

@@ -60,7 +60,7 @@ func (f *Feature) GetRESTAddr() string {
 
 // Config is the struct for the config.yaml setup file
 // todo: move this to a more common place, outside just tests
-// todo: can be moved to proto defination
+// todo: can be moved to proto definition
 type Config struct {
 	Chains   []*Chain   `name:"chains" json:"chains" yaml:"chains"`
 	Relayers []*Relayer `name:"relayers" json:"relayers" yaml:"relayers"`

clients/js/packages/client/__tests__/__snapshots__/client.config.test.ts.snap

@@ -42,7 +42,7 @@ sleep 2
 kubectl get pods --no-headers -o custom-columns=:metadata.name
 helm delete osmojs
 kubectl get pods --no-headers -o custom-columns=:metadata.name
-Log: All pods have been sucessfully terminated!"
+Log: All pods have been successfully terminated!"
 `;
 
 exports[`StarshipClient setup 2`] = `

clients/js/packages/client/__tests__/__snapshots__/client.ports.test.ts.snap

@@ -40,7 +40,7 @@ sleep 2
 kubectl get pods --no-headers -o custom-columns=:metadata.name
 helm delete osmojs
 kubectl get pods --no-headers -o custom-columns=:metadata.name
-Log: All pods have been sucessfully terminated!"
+Log: All pods have been successfully terminated!"
 `;
 
 exports[`StarshipClient setup 2`] = `

clients/js/packages/client/__tests__/__snapshots__/client.test.ts.snap

@@ -40,7 +40,7 @@ sleep 2
 kubectl get pods --no-headers -o custom-columns=:metadata.name
 helm delete osmojs
 kubectl get pods --no-headers -o custom-columns=:metadata.name
-Log: All pods have been sucessfully terminated!"
+Log: All pods have been successfully terminated!"
 `;
 
 exports[`StarshipClient setup 2`] = `

clients/js/packages/client/src/client.ts

@@ -606,7 +606,7 @@ export class StarshipClient implements StarshipClientI {
     });
 
     if (this.podStatuses.size === 0) {
-      this.log(chalk.green('All pods have been sucessfully terminated!'));
+      this.log(chalk.green('All pods have been successfully terminated!'));
       // once the pods are in done state, wait for 1 more seconds
       await new Promise((resolve) => setTimeout(resolve, 1000));
       return;

docs/pages/config/relayers.mdx

@@ -139,7 +139,7 @@ relayers:
 Available endpoints on
 * `rest` endpoints: https://hermes.informal.systems/documentation/rest-api.html?highlight=rest#rest-api
 * `exposer` endpoint
-  * `/create_channel` endpoint: Supports post request. Proto defination: https://github.com/hyperweb-io/starship/blob/main/starship/proto/exposer/service.proto#L47
+  * `/create_channel` endpoint: Supports post request. Proto definition: https://github.com/hyperweb-io/starship/blob/main/starship/proto/exposer/service.proto#L47
 
 One can use the exposer endpoint on the relayer to create channel from outside.
 Note: Still an experimental feature on exposer

examples/injective/README.md

@@ -89,7 +89,7 @@ Details of each of arguments in the config file can be found [here](https://docs
   * `configs/*.yaml`: Various config files as described above
 * `scripts/`: Handy scripts for dealing with starship setup and running
   * `scripts/dev-setup.sh`: Checks for dependencies
-  * `scripts/port-forward.sh`: Performs local port-forwarding based on config file definations
+  * `scripts/port-forward.sh`: Performs local port-forwarding based on config file definitions
   * `scripts/install.sh`: Installs helm chart in a connected kubernetes cluster
 * `Makefile`: Single entrypoint for Starship, has all commands needed
 * `READMD.md`: Readme file

examples/neutron/README.md

@@ -95,7 +95,7 @@ Details of each of arguments in the config file can be found [here](https://docs
   * `configs/scripts/`: Custom scripts used by the config file for setup. More details [here](https://docs.cosmology.zone/starship/config/chains#scripts-optional)
 * `scripts/`: Handy scripts for dealing with starship setup and running
   * `scripts/dev-setup.sh`: Checks for dependencies
-  * `scripts/port-forward.sh`: Performs local port-forwarding based on config file definations
+  * `scripts/port-forward.sh`: Performs local port-forwarding based on config file definitions
   * `scripts/install.sh`: Installs helm chart in a connected kubernetes cluster
 * `Makefile`: Single entrypoint for Starship, has all commands needed
 * `READMD.md`: Readme file

starship/cmd/starship/connect.go

@@ -200,7 +200,7 @@ func (c *Client) CheckKubectl() error {
 	return nil
 }
 
-// CheckPortForward verfify if all pods are in running state, and ready to be port-forwarded
+// CheckPortForward verify if all pods are in running state, and ready to be port-forwarded
 // * perform kubectl get pods
 // * check status of pods to be running based on the config
 // * return error if port-forwarding is not ready

starship/tests/e2e/config.go

@@ -40,7 +40,7 @@ type Feature struct {
 
 // Config is the struct for the config.yaml setup file
 // todo: move this to a more common place, outside of just tests
-// todo: can be moved to proto defination
+// todo: can be moved to proto definition
 type Config struct {
 	Chains   []*Chain   `name:"chains" json:"chains" yaml:"chains"`
 	Relayers []*Relayer `name:"relayers" json:"relayers" yaml:"relayers"`