Fix link to qubit picking heading

docs/tutorials/google/identifying_hardware_changes.ipynb

@@ -720,7 +720,7 @@
     "\n",
     "You've selected better candidate qubits for your circuit, based on updated information about the device. What else can you do for further improvements? \n",
     "\n",
-    "*    You need to map your actual circuit's logical qubits to your selected hardware qubits. This is in general a difficult problem, and the best solution can depend on the specific structure of the circuit to be run. Take a look at the [Qubit Picking with Loschmidt Echoes](./echoes.ipynb) tutorial, which estimates the error rates of gates for your specific circuit. Also, consider [Best Practices#Qubit picking](../../google/best_practices.ipynb#qubit-picking) for additional advice on this.\n",
+    "*    You need to map your actual circuit's logical qubits to your selected hardware qubits. This is in general a difficult problem, and the best solution can depend on the specific structure of the circuit to be run. Take a look at the [Qubit Picking with Loschmidt Echoes](./echoes.ipynb) tutorial, which estimates the error rates of gates for your specific circuit. Also, consider [Best Practices#Qubit picking](../../google/best_practices.ipynb#Qubit-picking) for additional advice on this.\n",
     "*    The [Optimization, Alignment, and Spin Echoes](./spin_echoes.ipynb) tutorial provides resources on how you can improve the reliability of your circuit by: optimizing away redundant or low-impact gates, aligning gates into moments with others of the same type, and preventing decay on idle qubits with by adding spin echoes. \n",
     "*    Other than for qubit picking, you should also use calibration for error compensation. The [XEB and Coherent Error](../../qcvv/xeb_coherent_noise.ipynb), [XEB Calibration Example](./xeb_calibration_example.ipynb), [Parallel XEB](../../qcvv/parallel_xeb.ipynb) and [Isolated XEB](../../qcvv/isolated_xeb.ipynb) tutorials demonstrate how to run a classical optimizer on collected two-qubit gate characterization data, identity the true unitary matrix implemented by each gate, and add [Virtual Pauli Z gates](../../google/devices.md#virtual-z-gates) to compensate for the identified error, improving the reliability of your circuit.\n",
     "*    You are also free to use the characterization data to improve the performance of large batches of experiment circuits. In this case you'd want to prepare your characterization ahead of running all your circuits, and use the data to compensate each circuit, right before running them. See [Calibration FAQ](../../google/calibration_faq.md#i-have-many-circuits-to-calibrate-how-do-i-speed-it-up) for more information. "