Revert "chore: Linting for markdown and js"

This reverts commit 1c92e0f655.

markdown/dev/guides/patterns/points/en.md

@@ -1,13 +1,12 @@
-***
-
+---
 title: Points
 order: 10
----------
+---
 
-\<Example
-part="docs\_overview"
-caption="Points store coordinates"
-options={{focus: "Points"}}
+<Example 
+  part="docs_overview" 
+  caption="Points store coordinates"
+  options={{focus: "Points"}}
 />
 
 Developing a pattern with FreeSewing is similar to doing it on paper.
@@ -17,24 +16,25 @@ Before we can draw any line, we need to know where it starts from, and where it
 That's why we have **points**. They are the most basic building block of a
 FreeSewing pattern, and their role is to store coordinates.
 
-Each point must have:
+Each point must have: 
 
-*   A **X-coordinate**
-*   A **Y-coordinate**
+ - A **X-coordinate**
+ - A **Y-coordinate**
 
 Together, these coordinates determine the location of the point in the 2-dimensional plane we're drawing on.
 
 <Note>
 
 Points are unlikely to confuse you. The only gotcha is [the
-coordinate system](/guides/prerequisites/coordinate-system/) which has a Y-axis that is inverted to what you
+coordinate system](/guides/prerequisites/coordinate-system/) which has a Y-axis that is inverted to what you 
 may intuitively expect.
 
 </Note>
 
 <Tip>
 
-Our example image (which, if you hadn't realized was created with FreeSewing) has a lot of
+Our example image (which, if you hadn't realized was created with FreeSewing) has a lot of 
 points in it. The corners of the boxes, the location where the text goes, and so on.
 
 </Tip>
+