Fix link to babel-parser and fix typo (#1182)

postcss · Sep 4, 2018 · acda7a5 · acda7a5
1 parent e1da8e9
commit acda7a5
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/architecture.md b/docs/architecture.md
@@ -54,7 +54,7 @@ That being said, there are few ways to write parser
  - *Split it into lexical analysis/parsing steps (source string → tokens → AST)*
 
     This is the way of how we do it in PostCSS and also the most popular one.
-    A lot of parsers like [`Babylon` (parser behind Babel)](https://github.com/babel/babel/tree/master/packages/babylon), [`CSSTree`](https://github.com/csstree/csstree) were written in such way.
+    A lot of parsers like [`@babel/parser` (parser behind Babel)](https://github.com/babel/babel/tree/master/packages/babel-parser), [`CSSTree`](https://github.com/csstree/csstree) were written in such way.
     The main reasons to separate tokenization from parsing steps are performance and abstracting complexity.
 
 Let think about why second way is better for our needs.

diff --git a/lib/postcss.d.ts b/lib/postcss.d.ts
@@ -411,7 +411,7 @@ declare namespace postcss {
     /**
      * Applies a SourceMap for a source file to the SourceMap. Each mapping to
      * the supplied source file is rewritten using the supplied SourceMap.
-     * Note: The resolution for the resulting mappings is the minimium of this
+     * Note: The resolution for the resulting mappings is the minimum of this
      * map and the supplied map.
      * @param sourceMapConsumer The SourceMap to be applied.
      * @param sourceFile The filename of the source file. If omitted, sourceMapConsumer