minor edits

timescale · Feb 15, 2023 · 9b541e0 · 9b541e0
1 parent 6f948cb
commit 9b541e0
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/_troubleshooting/timescaledb/pg_restore-errors.md b/_troubleshooting/timescaledb/pg_restore-errors.md
@@ -18,5 +18,5 @@ keywords: [backups, restore]
 * Copy this comment at the top of every troubleshooting page
 -->
  You might see the errors above when running `pg_restore`. When loading from a
- logical dump make sure you set `timescaledb.restoring` to true before loading
+ logical dump make sure that you set `timescaledb.restoring` to true before loading
  the dump.
diff --git a/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md b/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md
@@ -168,10 +168,10 @@ partitions, or the chunk interval sizes.
 
 </procedure>
 
-On a self hosted TimescaleDb instance with `postgres` superuser access you can
+On a self hosted TimescaleDB instance with `postgres` superuser access you can
 take a complete dump of all PostgreSQL databases in a cluster including global
 objects that are common to all databases, namely database roles, tablespaces,
-and privilege grants for configuration parameters using `pg_dumpall`. For more
+and privilege grants using `pg_dumpall`. For more
 information about how to use the `pg_dumpall` utility, see
 [PostgreSQL documentation][postgres-docs].