diff --git a/docs/dev_environment.md b/docs/dev_environment.md
--- a/docs/dev_environment.md
+++ b/docs/dev_environment.md
@@ -606,7 +606,7 @@
 
 ### Xcode settings
 
-First, in Xcode, open the Comm workspace `native/ios/Comm.xcworkspace`. Make sure that you’re signed into Xcode with an Apple Developer account (either the Comm developer team’s or your own). You can see any accounts currently associated with Xcode by navigating to Xcode → Preferences → Accounts.
+First, in Xcode, open the Comm workspace `native/ios/Comm.xcworkspace`. Make sure that you’re signed into Xcode with an Apple Developer account (either the Comm developer team’s or your own). You can see any accounts currently associated with Xcode by navigating to Xcode → Settings → Accounts.
 
 Next, you’ll want to ensure that the Comm project is configured with a valid Team, Bundle Identifier, and Provisioning Profile. To access these settings, navigate to View → Navigators → Project, and select the “Comm” project in the left sidebar. Then, select “Comm” from the “TARGETS” list, and navigate to the “Signing & Capabilities” tab. You should verify the following settings:
 
diff --git a/docs/nix_mobile_setup.md b/docs/nix_mobile_setup.md
--- a/docs/nix_mobile_setup.md
+++ b/docs/nix_mobile_setup.md
@@ -4,7 +4,7 @@
 
 ### Xcode settings
 
-First, in Xcode, open the Comm workspace `native/ios/Comm.xcworkspace`. Make sure that you’re signed into Xcode with an Apple Developer account (either the Comm developer team’s or your own). You can see any accounts currently associated with Xcode by navigating to Xcode → Preferences → Accounts.
+First, in Xcode, open the Comm workspace `native/ios/Comm.xcworkspace`. Make sure that you’re signed into Xcode with an Apple Developer account (either the Comm developer team’s or your own). You can see any accounts currently associated with Xcode by navigating to Xcode → Settings → Accounts.
 
 Next, you’ll want to ensure that the Comm project is configured with a valid Team, Bundle Identifier, and Provisioning Profile. To access these settings, navigate to View → Navigators → Project, and select the “Comm” project in the left sidebar. Then, select “Comm” from the “TARGETS” list, and navigate to the “Signing & Capabilities” tab. You should verify the following settings:
 
diff --git a/nix/start-powerline.sh b/nix/start-powerline.sh
--- a/nix/start-powerline.sh
+++ b/nix/start-powerline.sh
@@ -72,7 +72,7 @@
     elif [[ "$TERM_PROGRAM" == "iTerm.app" ]]; then
       echo ""
       echo "For glyph support, please:
-  Select iTerm2 > Preferences > Profiles > Text > Font > \
+  Select iTerm2 > Settings > Profiles > Text > Font > \
 Select font with 'for Powerline' in the name" >&2
       echo ""
     fi