Merge pull request #399 from lunasec-io/fix-typos-jan

Fix typos in docs

docs/blog/2021-12-22-story-lunasec.mdx

@@ -38,6 +38,8 @@ We want to make it known that there *are* ways to protect data against attacks l
 we've been building an Open Source framework to make it so these vulnerabilities, even full RCEs like Log4Shell, can't leak the sensitive data
 that attackers are really after. It feels more relevant now than ever.
 
+<!--truncate-->
+
 ## Modern attack surface
 In security, we use the word "attack surface" to talk about how much territory we need to defend.
 I think of this like the walls and gates around an ancient city. The bigger

docs/blog/2021-12-28-log4j-hype-train.mdx

@@ -34,8 +34,8 @@ in `2.16.0` and log4j was updated to `2.17.0` to fix it, another
 even *less* impactful [vulnerability](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44832) was discovered in
 `2.17.0`. I wonder if we should say "vulnerability" in quotes because
 this latest vulnerability requires an attacker to have access to the
-logger configuration file, which is a very privileged and unlikely scenario. It's so minor, we have chosen not to even
-flag this version it in our [log4shell scanning tool](/blog/log4j-zero-day-mitigation-guide). We hope the focus will remain on fixing
+logger configuration file, which is a very privileged and unlikely scenario. It's so minor, we have chosen not to
+scan for it in our [log4shell scanning tool](/blog/log4j-zero-day-mitigation-guide). We hope the focus will remain on fixing
 the far more critical vulnerabilities in earlier versions.
 
 In this post, we'll look at the motivations and repercussions of hyping up this far less serious attack vector. Then,

docs/typedoc-sidebar.js

@@ -14,4 +14,4 @@
  * limitations under the License.
  *
  */
-module.exports=[{type:'autogenerated',dirName:'cli-config'}];
+module.exports=[{type:'autogenerated',dirName:'react-sdk'}];