Commit c7759ab3 authored by James Ramsay's avatar James Ramsay

Change filenames to use underscores

parent 0748e128
......@@ -26,7 +26,7 @@ If you have lost your original primary, follow the
### Promote the secondary to primary
When initial replication is complete and the primary and secondary are closely in sync you can do a [Planned Failover](planned-fail-over.md)
When initial replication is complete and the primary and secondary are closely in sync you can do a [Planned Failover](planned_fail_over.md)
### Restore the secondary node
......
......@@ -23,7 +23,7 @@ immediately after following these instructions.
### Step 1. Allow replication to finish if possible
If the secondary is still replicating data from the primary, follow
[the Planned Failover doc](planned-fail-over.md) as closely as possible in
[the Planned Failover doc](planned_fail_over.md) as closely as possible in
order to avoid unnecessary data loss.
### Step 2. Permanently disable the primary
......
......@@ -53,7 +53,7 @@ improving speed for distributed teams
custom integrations and internal workflows
- Quickly fail-over to a Geo secondary in a
[Disaster Recovery](../administration/disaster_recovery/index.md) scenario
- Allows [planned fail-over](../administration/disaster_recovery/planned-fail-over.md) to a Geo secondary
- Allows [planned fail-over](../administration/disaster_recovery/planned_fail_over.md) to a Geo secondary
## Architecture
......
This document was moved to [another location](../administration/disaster_recovery/bring-primary-back.md).
This document was moved to [another location](../administration/disaster_recovery/bring_primary_back.md).
This document was moved to [another location](../administration/disaster_recovery/planned-fail-over.md).
This document was moved to [another location](../administration/disaster_recovery/planned_fail_over.md).
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment