anchor.diff:  [id="ca-certificate-error-in-console_{context}"]
   == CA certificate error in the {mtc-short} console
   
  -If a `CA certificate error` message is displayed the first time you try to access the {mtc-short} console, the likely cause is the use of self-signed CA certificates in one of the clusters.
  +If the {mtc-short} console displays a `CA certificate error` message the first time you try to access it, the likely cause is that a cluster uses self-signed CA certificates.
   
  -To resolve this issue, navigate to the `oauth-authorization-server` URL displayed in the error message and accept the certificate. To resolve this issue permanently, add the certificate to the trust store of your web browser.
  +Navigate to the `oauth-authorization-server` URL in the error message and accept the certificate. To resolve this issue permanently, install the certificate authority so that it is trusted.
   
  -If an `Unauthorized` message is displayed after you have accepted the certificate, navigate to the {mtc-short} console and refresh the web page.
  +If the browser displays an `Unauthorized` message after you have accepted the CA certificate, navigate to the {mtc-short} console and then refresh the web page.
   
   [id="oauth-timeout-error-in-console_{context}"]
   == OAuth timeout error in the {mtc-short} console
   
  -If a `connection has timed out` message is displayed in the {mtc-short} console after you have accepted a self-signed certificate, the causes are likely to be the following:
  +If the {mtc-short} console displays a `connection has timed out` message after you have accepted a self-signed certificate, the cause is likely to be one of the following:
   
   * Interrupted network access to the OAuth server
   * Interrupted network access to the {product-title} console
  -* Proxy configuration that blocks access to the `oauth-authorization-server` URL. See link:https://access.redhat.com/solutions/5514491[MTC console inaccessible because of OAuth timeout error] for details.
  +* Proxy configuration blocking access to the OAuth server. See link:https://access.redhat.com/solutions/5514491[MTC console inaccessible because of OAuth timeout error] for details.
   
  -You can determine the cause of the timeout.
  +To determine the cause:
   
  -.Procedure
  +* Inspect the {mtc-short} console web page with a browser web inspector.
  +* Check the `Migration UI` pod log for errors.
   
  -. Navigate to the {mtc-short} console and inspect the elements with the browser web inspector.
  -. Check the `MigrationUI` pod log:
  -+
  +[id="backup-storage-location-errors-in-velero-pod-log_{context}"]
  +== Backup storage location errors in the Velero pod log
  +
  +If a `Velero` `Backup` custom resource contains a reference to a backup storage location (BSL) that does not exist, the `Velero` pod log might display the following error messages:
  +
  +.BSL error messages
   [source,terminal]
   ----
  -$ oc logs <MigrationUI_Pod> -n openshift-migration
  +Error checking repository for stale locks
  +
  +Error getting backup storage location: backupstoragelocation.velero.io \"my-bsl\" not found
   ----
   
  -[id="podvolumebackups-timeout-error-in-velero-log_{context}"]
  -== PodVolumeBackups timeout error in Velero pod log
  +You can ignore these error messages. A missing BSL cannot cause a migration to fail.
   
  -If a migration fails because Restic times out, the following error is displayed in the `Velero` pod log.
  +[id="podvolumebackups-timeout-error-in-velero-log_{context}""]
  +== Pod volume backup timeout error in the Velero pod log
   
  -.Example output
  +If a migration fails because `Restic` times out, the `Velero` pod log displays the following error:
  +
  +.Pod volume backup timeout error
   [source,terminal]
   ----
  -level=error msg="Error backing up item" backup=velero/monitoring error="timed out waiting for all PodVolumeBackups to complete" error.file="/go/src/github.com/heptio/velero/pkg/restic/backupper.go:165" error.function="github.com/heptio/velero/pkg/restic.(*backupper).BackupPodVolumes" group=v1
  +level=error msg="Error backing up item" backup=velero/monitoring error="timed out
  +waiting for all PodVolumeBackups to complete" error.file="/go/src/github.com/
  +heptio/velero/pkg/restic/backupper.go:165" error.function="github.com/heptio/
  +velero/pkg/restic.(*backupper).BackupPodVolumes" group=v1
   ----
   
   The default value of `restic_timeout` is one hour. You can increase this parameter for large migrations, keeping in mind that a higher value may delay the return of error messages.
  
positive.code: +
  The output identifies the `Restic` pod that logged the errors.
  +
  .Example output
  [source,yaml]
  ----
    completionTimestamp: 2020-05-01T20:49:12Z
  
negative.code: 
  . Click *Save*.
  
  [id="resticverifyerrors-in-the-migmigration-custom-resource_{context}""]
  == Restic verification errors in the MigMigration custom resource
  
  If data verification fails when migrating a persistent volume with the file system data copy method, the `MigMigration` CR displays the following error:
  
  .MigMigration CR status
  [source,yaml]
  ----
  status:
  