Skip to content

Commit f1259df

Browse files
liamrossamiller-gh
authored andcommitted
fix: Fixed bold "Future Feature: ..." notes (#201).
1 parent 2a64dfa commit f1259df

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -319,7 +319,7 @@ Adding a `@block-reference` is as simple as this:
319319
:scope { block-name: block-2; }
320320
```
321321

322-
> 🔮 **Future Feature: Node Modules Block Resolution **
322+
> 🔮 **Future Feature: Node Modules Block Resolution**
323323
>
324324
> Whether you're integrating with a 3rd party library, or pulling in dependencies internal to your company, at some point you'll want to integrate with styles delivered via NPM! The resolution logic for `@block-reference`s to `node_modules` hasn't yet been implemented yet, but you can track progress (or even help out!) [over on Github](https://github.com/linkedin/css-blocks/issues/112).
325325
@@ -597,7 +597,7 @@ Here, we tell css-blocks to use the `color` value from `other.selector` instead
597597
}
598598
```
599599

600-
> 🔮 **Future Feature: Resolve All Shorthand **
600+
> 🔮 **Future Feature: Resolve All Shorthand**
601601
>
602602
> For straightforward resolutions where you just want to yield or assume full control of styling against another block, feel free to use the CSS `all` property to quickly override or yield to all property conflict with another block. The downside of doing this is that as new properties are added to another element, you don't get a chance to review them and decide:
603603

0 commit comments

Comments
 (0)