diff options
| -rw-r--r-- | content/learn/licenses.md | 2 | ||||
| -rw-r--r-- | content/learn/participate/derived-works.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/content/learn/licenses.md b/content/learn/licenses.md index 67e6e80..01e552d 100644 --- a/content/learn/licenses.md +++ b/content/learn/licenses.md @@ -36,7 +36,7 @@ on. Otherwise: To understand your obligations under any particular license, you will have to read it (and perhaps consult a lawyer, especially if you represent a business). However, most free software licenses have some traits in common with others, and -you get get a simple understanding of them by learning about a few essential +you can get a simple understanding of them by learning about a few essential traits. Here are some common features of free software licenses: ### Attribution diff --git a/content/learn/participate/derived-works.md b/content/learn/participate/derived-works.md index d135a50..1e5b082 100644 --- a/content/learn/participate/derived-works.md +++ b/content/learn/participate/derived-works.md @@ -21,7 +21,7 @@ into anything with relatively little obligation towards the copyright holders. Most permissive licenses require only that you include the license text, or even just a copyright statement, in your product. For free software projects which incorporate permissively licensed code into their work, meeting these -obligations is is usually as straightforward as including an additional license +obligations is usually as straightforward as including an additional license with your source code. When incorporating permissively licensed free software into non-free works, you |