networking doc: typo fixes

networking/v1alpha3/destination_rule.proto

@@ -118,7 +118,6 @@ message DestinationRule {
   // service. Traffic policies can be overridden at subset level.
   repeated Subset subsets = 3;
 
-  // $hide_from_docs
   // The resolution of a DestinationRule to apply to a service occurs in the
   // context of a hierarchy of namespaces. This rule controls whether those
   // namespaces are allowed to select this rule.

networking/v1alpha3/service_entry.proto

@@ -134,7 +134,7 @@ option go_package = "istio.io/api/networking/v1alpha3";
 //
 // The following example demonstrates the use of a dedicated egress gateway
 // through which all external service traffic is forwarded.
-// The 'export_to' field allows for control over the visibility of a service
+// The 'exportTo' field allows for control over the visibility of a service
 // declaration to other namespaces in the mesh. By default a service is exported
 // to all namespaces. The following example restricts the visibility to the
 // current namespace, represented by ".", so that it cannot be used by other
@@ -149,8 +149,8 @@ option go_package = "istio.io/api/networking/v1alpha3";
 // spec:
 //   hosts:
 //   - httpbin.com
-//   export_to:
-//   - .
+//   exportTo:
+//   - "."
 //   location: MESH_EXTERNAL
 //   ports:
 //   - number: 80
@@ -195,7 +195,7 @@ option go_package = "istio.io/api/networking/v1alpha3";
 // spec:
 //   hosts:
 //   - httpbin.com
-//   export_to:
+//   exportTo:
 //   - *
 //   gateways:
 //   - mesh
@@ -470,7 +470,6 @@ message ServiceEntry {
   // One or more endpoints associated with the service.
   repeated Endpoint endpoints = 6;
 
-  // $hide_from_docs
   // A list of namespaces to which this service is exported. Exporting a service
   // allows it to used by sidecars, gateways and virtual services defined in
   // other namespaces. This feature provides a mechanism for service owners
@@ -485,7 +484,7 @@ message ServiceEntry {
   // defines an export to all namespaces.
   //
   // For a Kubernetes Service the equivalent effect can be achieved by setting
-  // the annotation "networking.istio.io/export_to" to a comma-separated list
+  // the annotation "networking.istio.io/exportTo" to a comma-separated list
   // of namespace names.
   repeated string export_to = 7;
 

networking/v1alpha3/virtual_service.proto

@@ -176,7 +176,6 @@ message VirtualService {
   // matching an incoming request is used.
   repeated TCPRoute tcp = 4;
 
-  // $hide_from_docs
   // A list of namespaces to which this virtual service is exported. Exporting a
   // virtual service allows it to used by sidecars and gateways defined in
   // other namespaces. This feature provides a mechanism for service owners