Fix some typos

cmd/agentctl/main.go

@@ -152,8 +152,8 @@ func targetStatsCmd() *cobra.Command {
 
 	cmd := &cobra.Command{
 		Use:   "target-stats [WAL directory]",
-		Short: "Discover statitics on a specific target within the WAL.",
-		Long: `target-stats computes statitics on a specific target within the WAL at
+		Short: "Discover statistics on a specific target within the WAL.",
+		Long: `target-stats computes statistics on a specific target within the WAL at
 greater detail than the general wal-stats. The statistics computed is the
 cardinality of all series within that target.
 

docs/configuration-reference.md

@@ -330,7 +330,7 @@ grpc_client_config:
 ### global_config
 
 The `global_config` block configures global values for all launched Prometheus
-instanes.
+instances.
 
 ```yaml
 # How frequently should Prometheus instances scrape.

docs/getting-started.md

@@ -120,7 +120,7 @@ instance).
 When the Agent is run with this file, it will collect metrics from itself and
 send those metrics to the `remote_write` endpoint. All metrics will have (by
 default) an `agent_hostname` label equal to the hostname of the machine the
-Agent is running on. This label helps to uniquly identify the source of metrics
+Agent is running on. This label helps to uniquely identify the source of metrics
 if you run multiple Agent processes across multiple machines.
 
 Full configuration options can be found in the
@@ -274,7 +274,7 @@ docker run \
 
 ### Locally
 
-This section is only relavant if you installed the static binary of the
+This section is only relevant if you installed the static binary of the
 Agent. We do not yet provide system packages or configurations to run the Agent
 as a daemon process.
 

docs/maintaining.md

@@ -13,7 +13,7 @@ before releasing the Grafana Cloud Agent.
 #### Prerelease testing 
 
 For testing a release, run the [K3d example](../example/k3d/README.md) locally.
-Let it run for about 90 minutes, keeping an occassional eye on the Agent
+Let it run for about 90 minutes, keeping an occasional eye on the Agent
 Operational dashboard (noting that metrics from the scraping service will take
 time to show up). After 90 minutes, if nothing has crashed and you see metrics
 for both the scraping service and the non-scraping service, the Agent is ready

docs/operation-guide.md

@@ -26,7 +26,7 @@ isn't defined, the Agent will use Go's [os.Hostname](https://golang.org/pkg/os/#
 to determine the hostname.
 
 The following meta-labels are used to determine if a target is running on the
-same machine as the the target:
+same machine as the target:
 
 - `__address__`
 - `__meta_consul_node`
@@ -61,7 +61,7 @@ Prometheus service discovery, scraping, a WAL for storage, and `remote_write`.
 
 Instances allow for fine grained control of what data gets scraped and where it
 gets sent. Users can easily define two Instances that scrape different subsets
-of metrics and send them two two completely different remote_write systems.
+of metrics and send them to two completely different remote_write systems.
 
 Instances are especially relevant to the [scraping service
 mode](./scraping-service.md), where breaking up your scrape configs into

docs/overview.md

@@ -101,7 +101,7 @@ and metadata label propagation.
 While these features could theoretically be added to Telegraf as OSS contributions, 
 there would be a lot of forced hacks involved due to its current design.
 
-Additonally, Telegraf is a much larger project with its own goals for its community,
+Additionally, Telegraf is a much larger project with its own goals for its community,
 so any changes need to fit the general use cases it was designed for.
 
 With the Grafana Cloud Agent as its own project, we can deliver a more curated agent 

pkg/config/config.go

@@ -97,7 +97,7 @@ func Load(fs *flag.FlagSet, args []string) (*Config, error) {
 	return load(fs, args, LoadFile)
 }
 
-// load allows for tests to inject a function for retreiving the config file that
+// load allows for tests to inject a function for retrieving the config file that
 // doesn't require having a literal file on disk.
 func load(fs *flag.FlagSet, args []string, loader func(string, bool, *Config) error) (*Config, error) {
 	var (

pkg/integrations/manager.go

@@ -363,7 +363,7 @@ func (m *Manager) WireAPI(r *mux.Router) error {
 	return nil
 }
 
-// Stop stops the maanger and all of its integrations.
+// Stop stops the manager and all of its integrations.
 func (m *Manager) Stop() {
 	m.cancel()
 	<-m.done

pkg/prom/instance/instance.go

@@ -746,7 +746,7 @@ func getHash(data interface{}) (string, error) {
 // pulling metric values from a given metric name and label matchers.
 //
 // This is used by the agent instances to find the most recent timestamp
-// successfully remote_written to for pruposes of safely truncating the WAL.
+// successfully remote_written to for purposes of safely truncating the WAL.
 //
 // MetricValueCollector is only intended for use with Gauges and Counters.
 type MetricValueCollector struct {

pkg/tempo/promsdprocessor/prom_sd_processor.go

@@ -145,10 +145,10 @@ func (p *promServiceDiscoProcessor) watchServiceDiscovery() {
 	for {
 		// p.discoveryMgr.SyncCh() is never closed so we need to watch the context as well to properly exit this goroutine
 		select {
-		case targetGoups := <-p.discoveryMgr.SyncCh():
+		case targetGroups := <-p.discoveryMgr.SyncCh():
 			hostLabels := make(map[string]model.LabelSet)
-			level.Debug(p.logger).Log("msg", "syncing target groups", "count", len(targetGoups))
-			for jobName, groups := range targetGoups {
+			level.Debug(p.logger).Log("msg", "syncing target groups", "count", len(targetGroups))
+			for jobName, groups := range targetGroups {
 				p.syncGroups(jobName, groups, hostLabels)
 			}
 			p.mtx.Lock()

pkg/tempo/tempo.go

@@ -23,7 +23,7 @@ import (
 	"go.opentelemetry.io/collector/service/builder"
 )
 
-// Tempo wraps the OpenTelemetry collector to enablet tracing pipelines
+// Tempo wraps the OpenTelemetry collector to enable tracing pipelines
 type Tempo struct {
 	logger      *zap.Logger
 	metricViews []*view.View