fixes

Signed-off-by: Lee Calcote <lee.calcote@layer5.io>

Author: leecalcote

src/collections/blog/2020/2020-03-11-deploying-linkerd-with-meshery/index.mdx

@@ -35,10 +35,9 @@ import {Link} from "gatsby"
 <div>
   <div>
 
-<iframe width="100%" src="https://www.youtube.com/embed/MXQV-i-Hkf8" loading="lazy" frameborder="0"
-    allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture"
-    style="min-height: 315px; min-width: 280px;
-    "></iframe>
+
+<iframe width="100%" src="https://www.youtube.com/embed/MXQV-i-Hkf8" loading="lazy" frameBorder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" style={{minHeight: "315px", minWidth: "280px"}}></iframe>
+
 </div>
 But with so many mesh options around - how do we choose, evaluate and compare them? And once we’ve chosen a solution - how do we make it accessible to all our engineers? It is to provide an answer to these questions that the Layer5 community has created <Link to="/cloud-native-management/meshery">Meshery</Link>, the open-source, service mesh management plane. Meshery already supports a number of leading mesh providers with adapters for additional meshes on the way. In today’s video, I’ll show how to use Meshery for rolling out and evaluating Linkerd.
 
@@ -150,3 +149,4 @@ Happy meshing!
 
 
 </BlogWrapper>
+

src/collections/blog/2020/2020-05-21-getting-started-with-mesheryctl/index.mdx

@@ -153,7 +153,7 @@ We believe we have not missed any of the popular platforms for what it’s worth
 
 If you are thinking about the requirements you would have to run `mesheryctl`, so to your surprise, to successfully run `mesheryctl` you will only need :
 
-<table style={{ textAlign: "center" }} className="table-box"<tbody><tr><td className="text-centre">a running Docker daemon</td></tr></tbody></table>
+<table style={{ textAlign: "center" }} className="table-box"><tbody><tr><td className="text-centre">a running Docker daemon</td></tr></tbody></table>
 
 ### Into the MesheryCTL
 
@@ -182,7 +182,7 @@ Use "mesheryctl [command] --help" for more information about a command.
 
 Once you do `mesheryctl system start`, Meshery will pull its adapters and latest docker images. Meshery will also detect your Kubernetes configuration and will let you know if Kubernetes is running. Meshery will run it’s web-based user interface on localhost port `9081` and will let you select your choice of <a href="https://docs.meshery.io/extensibility#providers">Provider</a> before you can start managing your infrastructure with this powerful utility.
 
-<table style={{ textAlign: "center" }} className="table-box"<tbody><tr><td className="text-centre">One of the most interesting sub-commands of <code>mesheryctl</code> is <strong><code>perf</code></strong>.</td></tr></tbody></table>
+<table style={{ textAlign: "center" }} className="table-box"><tbody><tr><td className="text-centre">One of the most interesting sub-commands of <code>mesheryctl</code> is <strong><code>perf</code></strong>.</td></tr></tbody></table>
 
 The `perf` subcommand enables you to being managing the performance of your cloud native deployment and your workloads running atop of them. It lets you benchmark your infrastructure without using the Meshery UI from the command line interface itself. Once you type `mesheryctl perf`, it will present you with all the powerful flags you can control with CLI, including providing it with a `--file` flag that points to any of a number of performance test profiles that you may have saved.
 

src/collections/blog/2020/2020-06-01-meshery-accepted-into-cncf-landscape/index.mdx

@@ -68,3 +68,4 @@ For example - I sometimes wish I had more time and motivation to code new Mesher
 
 
 </BlogWrapper>
+

src/collections/blog/2020/2020-07-18-service-mesh-patterns-for-multitenancy/index.mdx

@@ -121,7 +121,7 @@ c. Ingress Gateway in the Worskpace 2 namespace for traffic entry point to the w
   profile: empty
   components:
   ingressGateways:
-  — name: wk1-ingressgw
+  - name: wk1-ingressgw
   namespace: workspace-1
   enabled: true
   label:
@@ -141,7 +141,7 @@ c. Ingress Gateway in the Worskpace 2 namespace for traffic entry point to the w
   profile: empty
   components:
   ingressGateways:
-  — name: wk2-ingressgw
+  - name: wk2-ingressgw
   namespace: workspace-2
   enabled: true
   label:
@@ -218,12 +218,12 @@ istiooperator.install.istio.io/wk2-gwconfig configured
   selector:
   istio: ingressgateway-1 # use istio gateway-1 controller in workspace-1
   servers:
-  — port:
+  - port:
   number: 80
   name: http
   protocol: HTTP
   hosts:
-  — “*”
+  - “*”
   $ cat istio/bookinfo-gateway-2.yaml
   apiVersion: networking.istio.io/v1alpha3
   kind: Gateway
@@ -233,12 +233,12 @@ istiooperator.install.istio.io/wk2-gwconfig configured
   selector:
   istio: ingressgateway-2 # use istio gateway-2 controller in workspace-1
   servers:
-  — port:
+  - port:
   number: 80
   name: http
   protocol: HTTP
   hosts:
-  — “*”
+  - “*”
   ```
 
 Deploy the applications in workspace-1 and workspace-2 and deploy the Gateway,VirtualService and DestinationRules.

src/collections/blog/2020/2020-11-17-layer5-at-kubecon-2020/index.mdx

@@ -89,3 +89,4 @@ with the specification.
 
 
 </BlogWrapper>
+

src/collections/blog/2021/2021-02-07-meshkit-and-meshery-adapter-library/index.mdx

@@ -24,7 +24,7 @@ import mesheryAdapterLibrary from "./meshery-adapter-library.svg";
 import malOverview from "./meshery-adapter-library-overview.webp";
 
 <BlogWrapper>
-<MeshkitMesheryAdapterLib>
+<MeshkitMesheryAdapterLib />
 
 <div className="intro">The Meshery v0.5.0 release includes two new libraries: <span>MeshKit</span> and <span>Meshery Adapter Library</span>.</div>