docs: link to where to buy commercial licenses

Author: SKalt

LICENSE.md

@@ -1,13 +1,14 @@
-`git-cc` is offered under the Indie Code Catalog Standard Deal, verion 4.0.1 or higher.
+`git-cc` is offered under the Indie Code Catalog Standard Deal, version 4.0.1 or higher.
 The text of the deal is available at https://indiecc.com/deal/4.0.1.
 The [Indie Code Catalog Standard Deal](#indie-code-catalog-standard-deal), [Free License](#indie-code-catalog-free-license), and [Paid License](#indie-code-catalog-paid-license) and are all copied below.
+You can buy a paid license at [https://indiecc.com/~skalt/git-cc](https://indiecc.com/~skalt/git-cc).
 
 Prior to 2021-08-25, `git-cc` was licensed under the strictEq free and paid licenses.
 You can view the previous licenses at commit [7ca8e95](https://github.com/SKalt/git-cc/blob/7ca8e95c1dc25ee87eeeb0d73f0b2ddef1aa9f29/LICENSE.md).
 If you bought a strictEq paid license, that license still grants you rights to copy and use updated versions `git-cc` even after the license change.
 The strictEq free license now only applies to versions of `git-cc` prior to the license change.
 
--------------------------------------------------------------------------------
+---
 
 # Indie Code Catalog Standard Deal
 
@@ -21,19 +22,19 @@ Everyone’s free to share the software, and to use it outside of business. Howe
 
 This page loosely summarizes two licenses: the free license that everyone gets and the paid license customers pay for. For the final work, read the license terms.
 
--------------------------------------------------------------------------------
+---
 
 # Indie Code Catalog Free License
 
 [Version 2.0.0](https://indiecc.com/free/2.0.0)
 
 ## Purpose
 
-This license allows you to use and share this software for [noncommercial purposes](#noncommercial) and [kids' projects](#kids-projects) for free, and to [try the software for commercial projects](#free-trials).  However, you have to [give credit](#give-credit) and [share any improvements you make](#share-improvements).
+This license allows you to use and share this software for [noncommercial purposes](#noncommercial) and [kids' projects](#kids-projects) for free, and to [try the software for commercial projects](#free-trials). However, you have to [give credit](#give-credit) and [share any improvements you make](#share-improvements).
 
 ## Acceptance
 
-To receive this license, you have to agree to its rules.  Those rules are both obligations to the developer and conditions to your license.  Don't do anything with the software against any rule you can't or won't follow.
+To receive this license, you have to agree to its rules. Those rules are both obligations to the developer and conditions to your license. Don't do anything with the software against any rule you can't or won't follow.
 
 ## Use
 
@@ -69,15 +70,15 @@ Give this software and the developer credit for contributing to projects you dev
 
 #### How to Give Credit
 
-Give credit in such a way that others can freely and readily find a written notice identifying this software and the developer, by name, as contributing to your project.  Do not do anything to stop others from sharing, publishing, or using those credits.
+Give credit in such a way that others can freely and readily find a written notice identifying this software and the developer, by name, as contributing to your project. Do not do anything to stop others from sharing, publishing, or using those credits.
 
 #### Conventions
 
-If widespread convention dictates a particular way to give credit for your kind of project, such as by end credit for a film, citation for an academic paper, acknowledgment for a book, or billing for a show, follow that convention.  For software provided to users to run on their own computers, give credit in documentation, notice files, and any "about" page or screen.  For software run as a service for users to access remotely, give credit in a `credits.txt` file according to <https://creditstxt.com>.
+If widespread convention dictates a particular way to give credit for your kind of project, such as by end credit for a film, citation for an academic paper, acknowledgment for a book, or billing for a show, follow that convention. For software provided to users to run on their own computers, give credit in documentation, notice files, and any "about" page or screen. For software run as a service for users to access remotely, give credit in a `credits.txt` file according to <https://creditstxt.com>.
 
 #### Who to Credit
 
-If the developer provides their name or the name of this software along with the software in a conventional way, such as in software package metadata or on an "about" page or screen, you may rely on the names they provide that way to be accurate and complete.  If the developer doesn't provide names that way, but includes a link to a homepage for this software, investigate that homepage for names to credit.  If the developer provides neither names to credit nor a link to a homepage, you do not have to do independent research to find names to credit.
+If the developer provides their name or the name of this software along with the software in a conventional way, such as in software package metadata or on an "about" page or screen, you may rely on the names they provide that way to be accurate and complete. If the developer doesn't provide names that way, but includes a link to a homepage for this software, investigate that homepage for names to credit. If the developer provides neither names to credit nor a link to a homepage, you do not have to do independent research to find names to credit.
 
 #### Declining Credit
 
@@ -87,7 +88,7 @@ On written request from the developer, remove their name, the name of this softw
 
 ### Share Improvements
 
-With two exceptions, [Prototypes](#prototypes) and [Applications](#applications), share all changes and additions you make to this software, as well as all software that invokes this software's functionality, with the developer.  When in doubt, share.
+With two exceptions, [Prototypes](#prototypes) and [Applications](#applications), share all changes and additions you make to this software, as well as all software that invokes this software's functionality, with the developer. When in doubt, share.
 
 #### Prototypes
 
@@ -101,19 +102,19 @@ You don't have to share any change, addition, or other software that meets all t
 
 #### Applications
 
-You don't have to share any software that only invokes this software's functionality through the interfaces this software exposes, unless it exposes so much of this software's interfaces or functionality to users, programmers, or other software that it becomes a practical substitute for this software.  Interfaces exposed by this software include all the interfaces this software provides users, programmers, or other software to invoke its functionality, such as command line, graphical, application programming, remote procedure call, and inter-process communication interfaces.
+You don't have to share any software that only invokes this software's functionality through the interfaces this software exposes, unless it exposes so much of this software's interfaces or functionality to users, programmers, or other software that it becomes a practical substitute for this software. Interfaces exposed by this software include all the interfaces this software provides users, programmers, or other software to invoke its functionality, such as command line, graphical, application programming, remote procedure call, and inter-process communication interfaces.
 
 #### How to Share
 
 To share software with the developer:
 
-1.  Send all the source code to the developer in the preferred form for making changes through the system the developer uses to manage and distribute the source code of this software.  If the developer uses a public source code repository that accepts pull requests, send a pull request.  If the developer accepts patches via e-mail, send a patch to their e-mail address or mailing list.
+1.  Send all the source code to the developer in the preferred form for making changes through the system the developer uses to manage and distribute the source code of this software. If the developer uses a public source code repository that accepts pull requests, send a pull request. If the developer accepts patches via e-mail, send a patch to their e-mail address or mailing list.
 
-2.  Make sure every new part of the source code is available under the Blue Oak Model License 1.0.0, the BSD-2-Clause Plus Patent License, or terms with substantially the same legal effect.  If you can choose the license terms for part of the source code, license it under the Blue Oak Model License 1.0.0.
+2.  Make sure every new part of the source code is available under the Blue Oak Model License 1.0.0, the BSD-2-Clause Plus Patent License, or terms with substantially the same legal effect. If you can choose the license terms for part of the source code, license it under the Blue Oak Model License 1.0.0.
 
 3.  Take these steps within thirty days.
 
-4.  Note that this license doesn't let you change the license for this software.  Follow [Notify of License](#notify-of-license).
+4.  Note that this license doesn't let you change the license for this software. Follow [Notify of License](#notify-of-license).
 
 ## Intellectual Property
 
@@ -127,7 +128,7 @@ The developer licenses you to do everything with the software that would otherwi
 
 ### Patent Defense
 
-If you make any written claim that this software or any other software offered through indiecc.com infringes or contributes to infringement of any patent, this license ends immediately.  If an organization you work for makes that kind of claim, this license ends immediately for work for that organization.
+If you make any written claim that this software or any other software offered through indiecc.com infringes or contributes to infringement of any patent, this license ends immediately. If an organization you work for makes that kind of claim, this license ends immediately for work for that organization.
 
 ## Excuse
 
@@ -141,7 +142,8 @@ The developer cannot revoke this license.
 
 <span class="conspicuous" markdown="1">As far as the law allows, the software comes as is, without any warranty or condition, and the developer will not be liable to anyone for any damages related to the software or this license, under any kind of legal claim.</span>
 
--------------------------------------------------------------------------------
+---
+
 # Indie Code Catalog Paid License
 
 [Version 3.0.1](https://indiecc.com/paid/3.0.1)
@@ -160,7 +162,7 @@ The developer cannot revoke this license.
 
 ## Versions
 
-This license covers the current version of the software as well as any new versions the developer might publish, until they publish a new version with a requirement to buy a separate license.  For example, if the current version of the software is 1.0.0, the developer publishes 1.1.0 in six months, and the developer publishes 1.2.0 six months after that, with a requirement to buy separate licenses for 1.2.0, this license covers versions 1.0.0 and 1.1.0, but not 1.2.0.
+This license covers the current version of the software as well as any new versions the developer might publish, until they publish a new version with a requirement to buy a separate license. For example, if the current version of the software is 1.0.0, the developer publishes 1.1.0 in six months, and the developer publishes 1.2.0 six months after that, with a requirement to buy separate licenses for 1.2.0, this license covers versions 1.0.0 and 1.1.0, but not 1.2.0.
 
 ## Personnel
 
@@ -178,11 +180,11 @@ To be covered by this license as customer personnel, you must be:
 
 ### Work
 
-This license covers personnel only in work for the customer or for its wholly owned subsidiaries.  This license does not cover personnel in work on personal projects or work for other organizations.
+This license covers personnel only in work for the customer or for its wholly owned subsidiaries. This license does not cover personnel in work on personal projects or work for other organizations.
 
 ### Responsibility
 
-Personnel have to follow all the rules of this license.  The customer agrees to stand legally responsible for any personnel that break those rules.
+Personnel have to follow all the rules of this license. The customer agrees to stand legally responsible for any personnel that break those rules.
 
 ## Sublicensing
 
@@ -210,7 +212,7 @@ To make sure everyone who gets a copy of the software knows about the terms for
 
 ## Payment
 
-In order to keep this license, your payment of `price` (USD) to the developer's agent has to go through and remain settled.  Denial, chargeback, or cancellation of the payment immediately ends this license.
+In order to keep this license, your payment of `price` (USD) to the developer's agent has to go through and remain settled. Denial, chargeback, or cancellation of the payment immediately ends this license.
 
 ## Copyright
 
@@ -222,11 +224,11 @@ The developer licenses the customer to do everything with the software that woul
 
 ## Agency
 
-The developer's agent sold this license on behalf of the developer.  The developer and the customer are legal "parties" to this license.  The developer's agent is not.
+The developer's agent sold this license on behalf of the developer. The developer and the customer are legal "parties" to this license. The developer's agent is not.
 
 ## Guarantees
 
-The developer guarantees that they own or have the rights to license copyrights in the software.  If the software invokes specific software dependencies, the developer guarantees that they have either been published under permissive license terms that Blue Oak Council rates "bronze" or better, or that their license terms have been noted in documentation published with the software.
+The developer guarantees that they own or have the rights to license copyrights in the software. If the software invokes specific software dependencies, the developer guarantees that they have either been published under permissive license terms that Blue Oak Council rates "bronze" or better, or that their license terms have been noted in documentation published with the software.
 
 ## Disclaimer
 

README.md

@@ -39,6 +39,16 @@ The conventional commits standard helps figure out what to write.
 As a bonus, conventional commits facilitate generating changelogs and semantic version increments.
 An interactive command-line application helps with following the standard.
 
+## Licensing
+
+`git-cc` is source-provided software, not free software:
+
+> To use software listed on this site to make money or for work, you need to buy a license. If you’re part of a team, everyone on your team who uses the software needs to buy one. You can [try before you buy](#free-trials), to make sure the software works and integrates well with your prototypes.
+
+For more details, see [./LICENSE.md](./LICENSE.md).
+
+You can buy a paid license at [https://indiecc.com/~skalt/git-cc](https://indiecc.com/~skalt/git-cc).
+
 ## Installation
 
 Go to [the project releases page][releases page] to download the appropriate package. Alternately, use the installer script at [./scripts/install.sh](./scripts/install.sh).