Skip to content

Commit fe81a10

Browse files
authored
Merge pull request #978 from MatheusMCuba/patch-1
Simple Grammar Corrections
2 parents 2740f14 + 65f3238 commit fe81a10

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

.github/CONTRIBUTING.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
PRs to this project are welcome, but before contributing please bear in mind my thoughts below. If you want to get involved but are unsure, please ask (say hello in the [Gitter chat room](http://gitter.im/ButchersBoy/MaterialDesignInXamlToolkit)). Also note I wrote these guidelines several months after the library was first made available, with the benefit of hindsight. Apologies if there are inconsistencies with what you read below and what's already in the library.
44

5-
## The purpose of this libary:
5+
## The purpose of this library:
66

77
This is a theme library, **not** a control library. There is a subtle difference. Yes, there are some new custom controls, but their role is to specifically support either styling of existing WPF controls, or to Material Design components, as per the "Components" section in [Google's guidelines](https://www.google.com/design/spec/material-design/introduction.html).
88

@@ -22,8 +22,8 @@ This whole project is a personal hobby, and this is even more true of the UWP se
2222

2323
## TabControl:
2424

25-
There is no TabControl style, I won't create one, and I wont accept one. I have Dragablz, and don't want the added burden of supporting two styles; even if it is fully complete. I don't want the duplication and the overhead.
25+
There is no TabControl style, I won't create one, and I wont accept one. I have Dragablz and don't want the added burden of supporting two styles; even if it is fully complete. I don't want the duplication and the overhead.
2626

2727
## Submitting a PR:
2828

29-
Probably the smaller the better (within sensible bounds for the nature of your change); at least keep a single feature to a single branch/PR.
29+
Probably the smaller the better (within sensible bounds for the nature of your change); at least keep a single feature to a single branch/PR.

0 commit comments

Comments
 (0)