Address feedback…

…and fix some URLs that were linking to `localhost`.

Author: savetheclocktower

docs/getting-started/installing-pulsar.md

@@ -117,7 +117,7 @@ Pulsar on Windows supports a standard installation as well as running Pulsar in
 
 To install Pulsar regularly, download the `Setup` file, and double click to run. During the installation process, you’ll be able to choose either the default user install (just the current user) or a machine install (all users of the machine). A user install is recommended, but either one will work, though a machine install will require administrative privileges.
 
-You’ll be asked whether the folders that contain the `pulsar` and `ppm` binaries should be added to your `PATH`. This is recommended; it will make it easier to [launch Pulsar from a terminal](http://localhost:8081/getting-started/terminal-commands/).
+You’ll be asked whether the folders that contain the `pulsar` and `ppm` binaries should be added to your `PATH`. This is recommended; it will make it easier to [launch Pulsar from a terminal](/getting-started/terminal-commands/).
 
 :::note
 

docs/ide-features/builtin-packages.md

@@ -29,7 +29,7 @@ Even where other autocompletion providers exist — like the built-in {autocompl
 
 ## Symbol resolution
 
-We briefly mentioned how you can [navigate through files by symbol](http://localhost:8082/using-pulsar/movement/#navigating-by-symbols). Those symbols could be a number of things depending on the kind of file: method names, CSS selectors, or Markdown heading names, to list a few examples.
+We briefly mentioned how you can [navigate through files by symbol](/using-pulsar/movement/#navigating-by-symbols). Those symbols could be a number of things depending on the kind of file: method names, CSS selectors, or Markdown heading names, to list a few examples.
 
 This functionality is supplied by the built-in {symbols-view} package. Even without an IDE package, Pulsar allows you to navigate by symbols in most languages for the current file. (Since the file is already open, this isn’t hard!) But `symbols-view` also has the ability to jump to a symbol in a _different_ file, but not automatically; it needs something to tell it what those symbols are. A language server can do that very thing!
 

docs/ide-features/getting-started.md

@@ -92,7 +92,7 @@ If you’ve got experience with JavaScript or have read through [our package tut
 
 The whole point of a language server is to reduce the implementation burden on code editors, since most of the “glue” code is shared across language servers. For that reason, we maintain [a library called `atom-languageclient`](https://github.com/savetheclocktower/atom-languageclient) designed to make it easy to [connect a language server to Pulsar](https://github.com/savetheclocktower/atom-languageclient?tab=readme-ov-file#developing-packages). With practice, you can do it in about a half-hour!
 
-If you’re not comfortable writing JavaScript, [reach out to us](https://pulsar-edit.dev/community) instead. Creating an IDE package for Pulsar is easier than you think! We can often coach you through the process, or perhaps even write it for you.
+If you’re not comfortable writing JavaScript, [reach out to us](https://pulsar-edit.dev/community) instead. Creating an IDE package for Pulsar is easier than you think! We can often coach you through the process or help you find collaborators.
 
 [PHP]: https://php.net
 [ERB]: https://github.com/ruby/erb?tab=readme-ov-file#erb

docs/troubleshooting-pulsar/using-safe-mode.md

@@ -3,10 +3,7 @@ title: Using safe mode
 layout: doc.ejs
 ---
 
-A large part of Pulsar’s functionality comes from packages you can install.
-Pulsar will also execute the code in your [init script](/customizing-pulsar/the-init-file) on
-startup. In some cases, these packages and the code in the init script might be
-causing unexpected behavior, problems, or performance issues.
+A large part of Pulsar’s functionality comes from packages you can install. Pulsar will also execute the code in your [init script](/customizing-pulsar/the-init-file) on startup. In some cases, these packages and the code in the init script might be causing unexpected behavior, problems, or performance issues.
 
 To determine if that is happening, start Pulsar from the terminal in safe mode:
 
@@ -16,6 +13,6 @@ $ pulsar --safe
 
 This starts Pulsar, but does not load packages from <span class="platform-mac platform-linux">`~/.pulsar/packages` or `~/.pulsar/dev/packages`</span> <span class="platform-win">`%USERPROFILE%\.pulsar\packages` or `%USERPROFILE%\.pulsar\dev\packages`</span> and disables loading of your init script. If you can no longer reproduce the problem in safe mode, it’s likely it was caused by one of the packages or the init script.
 
-If removing or commenting out all content from the init script and starting Pulsar normally still produces the error, then try figuring out which package is causing trouble. Start Pulsar normally again and [open the settings view](http://localhost:8081/using-pulsar/basics/#settings-and-preferences) with <kbd class="platform-linux platform-win">Ctrl+,</kbd><kbd class="platform-mac">Cmd+,</kbd>. Since the settings view allows you to disable each installed package, you can disable packages one by one until you can no longer reproduce the issue. Restart Pulsar or reload Pulsar with <kbd class="platform-linux platform-win">Ctrl+Shift+F5</kbd><kbd class="platform-mac">Alt+Cmd+Ctrl+L</kbd> after you disable each package to make sure it’s completely gone.
+If removing or commenting out all content from the init script and starting Pulsar normally still produces the error, then try figuring out which package is causing trouble. Start Pulsar normally again and [open the settings view](/using-pulsar/basics/#settings-and-preferences) with <kbd class="platform-linux platform-win">Ctrl+,</kbd><kbd class="platform-mac">Cmd+,</kbd>. Since the settings view allows you to disable each installed package, you can disable packages one by one until you can no longer reproduce the issue. Restart Pulsar or reload Pulsar with <kbd class="platform-linux platform-win">Ctrl+Shift+F5</kbd><kbd class="platform-mac">Alt+Cmd+Ctrl+L</kbd> after you disable each package to make sure it’s completely gone.
 
 When you find the problematic package, you can disable or uninstall the package. We strongly recommend creating an issue on the package’s GitHub repository.