Regenerate two md files (#47183)

doc/admin/observability/alerts.md

@@ -2355,7 +2355,7 @@ Generated query for critical alert: `min((pg_up) <= 0)`
 
 **Next steps**
 
-- Drop and re-create the invalid trigger—please contact Sourcegraph to supply the trigger definition.
+- Drop and re-create the invalid trigger - please contact Sourcegraph to supply the trigger definition.
 - More help interpreting this metric is available in the [dashboards reference](./dashboards.md#postgres-invalid-indexes).
 - **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert:
 
@@ -2417,7 +2417,7 @@ Generated query for warning alert: `max((pg_exporter_last_scrape_error) >= 1)`
 
 **Next steps**
 
-- The database migration has been in progress for 5 or more minutes—please contact Sourcegraph if this persists.
+- The database migration has been in progress for 5 or more minutes - please contact Sourcegraph if this persists.
 - More help interpreting this metric is available in the [dashboards reference](./dashboards.md#postgres-migration-in-progress).
 - **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert:
 

doc/dev/background-information/sg/reference.md

@@ -275,9 +275,9 @@ Flags:
 
 Get logs from CI builds (e.g. to grep locally).
 
-Get logs from CI builds, and output them in stdout or push them to Loki. By default only gets failed jobs—to change this, use the '--state' flag.
+Get logs from CI builds, and output them in stdout or push them to Loki. By default only gets failed jobs - to change this, use the '--state' flag.
 
-The '--job' flag can be used to narrow down the logs returned—you can provide either the ID, or part of the name of the job you want to see logs for.
+The '--job' flag can be used to narrow down the logs returned - you can provide either the ID, or part of the name of the job you want to see logs for.
 
 To send logs to a Loki instance, you can provide --out=http://127.0.0.1:3100 after spinning up an instance with 'sg run loki grafana'.
 From there, you can start exploring logs with the Grafana explore panel.
@@ -688,7 +688,7 @@ Flags:
 
 ### sg migration upto
 
-Ensure a given migration has been applied—may apply dependency migrations.
+Ensure a given migration has been applied - may apply dependency migrations.
 
 Available schemas:
 
@@ -713,7 +713,7 @@ Flags:
 
 ### sg migration undo
 
-Revert the last migration applied—useful in local development.
+Revert the last migration applied - useful in local development.
 
 Available schemas:
 
@@ -732,7 +732,7 @@ Flags:
 
 ### sg migration downto
 
-Revert any applied migrations that are children of the given targets—this effectively "resets" the schema to the target version.
+Revert any applied migrations that are children of the given targets - this effectively "resets" the schema to the target version.
 
 Available schemas:
 
@@ -1038,7 +1038,7 @@ Also refer to the generated reference documentation available for site admins:
 
 ### sg monitoring generate
 
-Generate monitoring assets—dashboards, alerts, and more.
+Generate monitoring assets - dashboards, alerts, and more.
 
 ```sh
 # Generate all monitoring with default configuration into a temporary directory
@@ -1442,7 +1442,7 @@ Flags:
 
 ## sg page
 
-Page engineers at Sourcegraph—mostly used within scripts to automate paging alerts.
+Page engineers at Sourcegraph - mostly used within scripts to automate paging alerts.
 
 ```sh
 $ sg page --opsgenie.token [TOKEN] --message "something is broken" [my-schedule-on-ops-genie]