Update docs to change 'master' to 'main'.

Author: kwwall

CONTRIBUTING-TO-ESAPI.txt

@@ -31,9 +31,9 @@ Overview:
     We are following the branching model described in
         https://nvie.com/posts/a-successful-git-branching-model
     If you are unfamiliar with it, you would be advised to give it a
-    quick perusal. The major point is that the 'master' branch is reserved for
-    official releases (which will be tagged), the 'develop' branch is used for
-    ongoing development work and is the default branch, and we generally work
+    quick perusal. The major point is that the 'main' (formerly 'master') branch
+    is reserved for official releases (which will be tagged), the 'develop' branch is
+    used for ongoing development work and is the default branch, and we generally work
     off 'issue' branches named 'issue-#' where # is the GitHub issue number.
     (The last is not an absolute requirement, but rather a suggested
     approach.)
@@ -74,7 +74,7 @@ Steps to work with ESAPI:
 
     But the basic high level steps are:
     1. Fork https://github.com/ESAPI/esapi-java-legacy to your own GitHub
-       repository.
+       repository using the GitHub web site.
     2. On your local laptop, clone your own GitHub ESAPI repo (i.e, the
        forked repo created in previous step)
     3. Create a new branch to work on an issue. I usually name the branch

README.md

@@ -22,7 +22,7 @@ You can find the OWASP ESAPI wiki pages at [https://owasp.org/www-project-enterp
 You will find that GitHub repository at [https://github.com/ESAPI/esapi-java-legacy](https://github.com/ESAPI/esapi-java-legacy).
 
 <b>IMPORTANT NOTES:</b>
-The default branch for ESAPI legacy is now the 'develop' branch (rather than the 'master' branch), where future development, bug fixes, etc. will now be done. The 'master' branch is now marked as "protected"; it reflects the latest stable ESAPI release (2.1.0.1 as of this date). Note that this change of making the 'develop' branch the default may affect any pull requests that you were intending to make.
+The default branch for ESAPI legacy is now the 'develop' branch (rather than the 'main' (formerly 'master') branch), where future development, bug fixes, etc. will now be done. The 'main' branch is now marked as "protected"; it reflects the latest stable ESAPI release (2.1.0.1 as of this date). Note that this change of making the 'develop' branch the default may affect any pull requests that you were intending to make.
 
 Also, the <i>minimal</i> baseline Java version to use ESAPI is Java 7. (This was changed from Java 6 during the 2.2.0.0 release.)