Fix some comments (#3119)

Signed-off-by: goodmost <[email protected]>

Author: goodmost

docs/sources/view-and-analyze-profile-data/flamegraphs.md

@@ -29,7 +29,7 @@ Horizontally, the flamegraph represents 100% of the time that this application w
 The width of each node represents the amount of time spent in that function.
 The wider the node, the more time spent in that function. The narrower the node, the less time spent in that function.
 
-Vertically, the nodes in the flamegraph represent the heirarchy of which functions were called and how much time was spent in each function.
+Vertically, the nodes in the flamegraph represent the hierarchy of which functions were called and how much time was spent in each function.
 The top node is the root node and represents the total amount of time spent in the application.
 The nodes below it represent the functions that were called and how much time was spent in each function.
 The nodes below those represent the functions that were called from those functions and how much time was spent in each function.

docs/sources/view-and-analyze-profile-data/pyroscope-ui.md

@@ -83,7 +83,7 @@ The Comparison page facilitates side-by-side comparison of profiles either based
 
 To run a comparison:
 
-1. Select two different sets of labels (for exmaple, `env:production` vs. `env:development`) and or time periods, reflected by the sub-timelines above each flamegraph.
+1. Select two different sets of labels (for example, `env:production` vs. `env:development`) and or time periods, reflected by the sub-timelines above each flamegraph.
 2. View the resulting flamegraphs side by side to identify disparities in performance.
 
 There are many practical use cases for comparison for companies using Pyroscope.

ebpf/bpf/libbpf/bpf_helper_defs.h

@@ -3773,7 +3773,7 @@ static struct socket *(*bpf_sock_from_file)(struct file *file) = (void *) 162;
  * 	actual packet size (resulting in negative packet size) will in
  * 	principle not exceed the MTU, why it is not considered a
  * 	failure.  Other BPF-helpers are needed for performing the
- * 	planned size change, why the responsability for catch a negative
+ * 	planned size change, why the responsibility for catch a negative
  * 	packet size belong in those helpers.
  *
  * 	Specifying *ifindex* zero means the MTU check is performed

ebpf/bpf/pystr.h

@@ -31,8 +31,8 @@ struct _object {
 
 
 // Note: it is incomplete
-// Some state fields may be ommited
-// Also wstr field is ommited
+// Some state fields may be omitted
+// Also wstr field is omitted
 // Only first 32 bytes  are here
 typedef struct {
     struct _object                   ob_base;              /*     0    16 */

public/app/components/QueryInput/QueryInput.module.scss

@@ -42,7 +42,7 @@
 
   // We use !important so that we can overwrite the classes from
   // pre[class*="language-"]
-  // which from from prism.scss
+  // which from prism.scss
   background: none !important;
   padding: 0 !important;
   margin: 0 !important;

public/app/legacy/models/spyName.ts

@@ -15,7 +15,7 @@ export const SpyNameFirstClass = [
 ] as const;
 
 export const SpyNameOther = [
-  'scrape', // for compability purposes, it should be golang
+  'scrape', // for compatibility purposes, it should be golang
   'tracing',
   'unknown',
 ] as const;

public/app/sass/sanitize.css/CHANGELOG.md

@@ -21,7 +21,7 @@
 - Added: Opinionated `border` removal on iframes in all browsers.
 - Removed: Opinionated `border-radius` on form controls.
 - Removed: Opinionated `box-shadow` on form controls to match UA expectations.
-- Fixed: `Edge` comments without `Chrome` are are changed to `Edge 18-`.
+- Fixed: `Edge` comments without `Chrome` are changed to `Edge 18-`.
 - Fixed: `Chrome` comments without `Edge` have `Edge` added.
 - Fixed: Nested list `dl` normalizations split.
 - Fixed: Logical `margin-block` normalization changed to `margin`.

public/app/services/base.ts

@@ -98,7 +98,7 @@ async function connectRequest(
     // We could parse the response
     return Result.ok(data);
   } catch (e) {
-    // We couldn't parse, but there's definitly some data
+    // We couldn't parse, but there's definitely some data
     return Result.err(
       new ResponseOkNotInJSONFormat(response.value.status, textBody)
     );
@@ -181,7 +181,7 @@ async function fetchAndHandleErrors(
       )
     );
   } catch (e) {
-    // We couldn't parse, but there's definitly some data
+    // We couldn't parse, but there's definitely some data
     // We must handle this case since the go server sometimes responds with plain text
 
     // It's HTML

public/app/util/formatDate.ts

@@ -72,7 +72,7 @@ function isValidDate(d: Date) {
  * based on the passed-in parameter value
  * which is either a Number repsenting a date
  * or a default preset(example: "now-1h")
- * this is neccessary because the DatePicker component
+ * this is necessary because the DatePicker component
  * from react-datepicker package has a property (selected)
  * that requires an input of type Date if we passed another
  * type the Component will throw an error and the app will crash

public/app/util/randomId.ts

@@ -1,6 +1,6 @@
 /**
  * generates a random ID to be used outside react-land (eg jquery)
- * it's mandatory to generate it once, preferrably on a function's body
+ * it's mandatory to generate it once, preferably on a function's body
  * IMPORTANT: it does NOT:
  * - generate unique ids across server/client
  *   use `useId` instead (https://reactjs.org/docs/hooks-reference.html#useid)