Fix links

Author: kgremban

articles/iot-operations/connect-to-cloud/concept-schema-registry.md

@@ -28,13 +28,6 @@ Schema registry expects the following required fields in a message schema:
 | `type` | `Object` |
 | `properties` | The message definition. |
 
-Additionally, you can include optional fields in your message schema as long as they conform with the schema type. For example:
-
-| Optional field | Definition |
-| `name` | A name for the schema. |
-| `description` | A description of the schema. |
-| `required` | A list of properties required to be present in the messages. |
-
 ### Sample schemas
 
 The following sample schemas provide examples for defining message schemas in each format.

articles/iot-operations/connect-to-cloud/overview-dataflow.md

@@ -65,7 +65,7 @@ Schema registry, a feature provided by Azure Device Registry Preview, is a synch
 
 Dataflows uses messages schemas at both the source and destination points. For sources, message schemas can work as filters to identify the specific messages that you want to capture for a dataflow. For destinations, message schemas help to transform the message into the format expected by the destination endpoint.
 
-For more information, see [Understand message schemas](./howto-schema-registry.md).
+For more information, see [Understand message schemas](./concept-schema-registry.md).
 
 ## Related content
 

articles/iot-operations/toc.yml

@@ -100,7 +100,7 @@ items:
         - name: Enrich data
           href: connect-to-cloud/concept-dataflow-enrich.md
       - name: Use message schemas
-        href: connect-to-cloud/howto-schema-registry.md
+        href: connect-to-cloud/concept-schema-registry.md
       - name: Manage dataflow profile
         href: connect-to-cloud/howto-configure-dataflow-profile.md
     - name: Manage layered network