Replace remaining coreos.com links

Author: bgilbert

architecture/understanding-development.adoc

@@ -297,7 +297,7 @@ link:https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/[daemon
 You can also run a daemon set on a subset of nodes, based on node labels.
 * Require life-cycle management. When you want to hand off your application so
 that others can use it, consider creating an
-link:https://coreos.com/operators/[Operator]. Operators let you build in
+link:https://www.openshift.com/learn/topics/operators[Operator]. Operators let you build in
 intelligence, so it can handle things like backups and upgrades automatically.
 Coupled with the Operator Lifecycle Manager (OLM), cluster managers can expose
 Operators to selected namespaces so that users in the cluster can run them.

modules/compliance-review.adoc

@@ -35,7 +35,7 @@ status:
 
 The remediation payload is stored in the `spec.current` attribute. The payload can be any Kubernetes object, but because this remediation was produced by a node scan, the remediation payload in the above example is a `MachineConfig` object. For Platform scans, the remediation payload is often a different kind of an object (for example, a `ConfigMap` or `Secret` object), but typically applying that remediation is up to the administrator, because otherwise the Compliance Operator would have required a very broad set of permissions to manipulate any generic Kubernetes object. An example of remediating a Platform check is provided later in the text.
 
-To see exactly what the remediation does when applied, the `MachineConfig` object contents use the Ignition objects for the configuration. Refer to the link:https://coreos.com/ignition/docs/latest/configuration-v2_2.html[Ignition specification] for further information about the format. In our example, `the spec.config.storage.files[0].path` attribute specifies the file that is being create by this remediation (`/etc/sysctl.d/75-sysctl_net_ipv4_conf_all_accept_redirects.conf`) and the `spec.config.storage.files[0].contents.source` attribute specifies the contents of that file.
+To see exactly what the remediation does when applied, the `MachineConfig` object contents use the Ignition objects for the configuration. Refer to the link:https://coreos.github.io/ignition/specs/[Ignition specification] for further information about the format. In our example, `the spec.config.storage.files[0].path` attribute specifies the file that is being create by this remediation (`/etc/sysctl.d/75-sysctl_net_ipv4_conf_all_accept_redirects.conf`) and the `spec.config.storage.files[0].contents.source` attribute specifies the contents of that file.
 
 [NOTE]
 ====