Merge branch 'main' of https://github.com/AztecProtocol/docs

docs/docs/sdk/usage/setup.mdx

@@ -42,6 +42,12 @@ Once the provider is set up you can create an instance of the Aztec SDK, specify
 https://api.aztec.network/aztec-connect-testnet/falafel
 ```
 
+You can connect to the Aztec rollup provider that is connected to Ethereum at:
+
+```shell
+https://api.aztec.network/aztec-connect-prod/falafel
+```
+
 ```ts title="/src/latest/index.ts"
 const setupSdk = async () => {
   sdk = await createAztecSdk(walletProvider, {

docs/docs/zk-money/troubleshooting.md

@@ -1,10 +1,28 @@
 # Troubleshooting Guide
 
+## Account Not Registered Error
+
+Most "Account Not Registered" errors can be resolved with one of two methods:
+
+1) Double-checking your Ethereum address. Please connect to zk.money using the Ethereum address you used to sign up for your alias.
+
+2) Mistyping or misremembering your alias. Remember that your alias is critical to access your account and forgetting or misplacing it means you may not be able to access your funds.
+
+If either approach does not work, you may belong to one of the below cohorts whose account aliases were not migrated:
+
+1) Users who registered **prior** to July, 2021 but **did not do an account migration in the old system**. From July, 2021 to June, 2022, accounts were required to undergo an account migration that incremented user account nonces by 1. If you did not migrate prior to June, 2022, your alias was not moved to the new system. This includes users who attempted migration on old.zk.money after June, 2022.
+
+2) Users who forgot their alias after June, 2022 and had to go through the "Forgot alias" flow on old.zk.money. If you forgot your alias for old.zk.money and recovered your account using the "Forgot alias" flow, including registering a new alias, the new alias will NOT be migrated. Your old (forgotten) alias **has** been migrated if you want to try remembering it in the new system.
+
+###
+
 ## Hung on "Connecting to Rollup Provider" on sign-up or log-in
 
-You may be presented with an "AbortError: Transaction Aborted" when attempted to sign up or log-in after a system update.
+If you see "Connecting to Rollup Provider" for more than 60 seconds, please troubleshoot using the below steps.
+
+You may also be presented with an "AbortError: Transaction Aborted" when attempted to sign up or log-in after a system update.
 
-In that case, navigate to your browser console (F12 or Alt-Cmd-J) and the Application tab on the top bar. Once there, click "Storage" under the "Application" group and click "Clear site data." Refresh the page.
+In either case, navigate to your browser console (F12 or Alt-Cmd-J) and the Application tab on the top bar. Once there, click "Storage" under the "Application" group and click "Clear site data." Refresh the page.
 
 ![image](https://user-images.githubusercontent.com/15220860/177643292-e39ce717-8a58-4916-ad51-74e10c7685d4.png)