Replace "itext7" to simple "itext"

DEVSIX-7365

Autoported commit.
Original commit hash: [e2d1bf9]
Manual files:
CONTRIBUTING.md
README.md

Author: introfog

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to iText 7 Community
+# Contributing to iText Community
 
-We'd love for you to contribute to our source code and to make **iText 7 Community** even better than it is
+We'd love for you to contribute to our source code and to make **iText Community** even better than it is
 today! Here are the guidelines we'd like you to follow:
 
  - [Question or Problem?](#question)
@@ -15,7 +15,7 @@ today! Here are the guidelines we'd like you to follow:
 
 ## <a name="question">Got a Question or Problem?</a>
 
-If you have questions about how to use **iText 7 Community**, please direct these to [Stack Overflow][stackoverflow].
+If you have questions about how to use **iText Community**, please direct these to [Stack Overflow][stackoverflow].
 
 If you are a customer with a [support agreement][support], you also have direct access to our JIRA and our developers.
 
@@ -79,7 +79,7 @@ Before you submit your pull request consider the following guidelines:
 * Build your changes locally to ensure all the tests pass.
 * Push your changes to your GitHub account.
 * Create a pull request in GitHub.
-"Head fork" should be your repository, and the "base fork" should be the iText7 official repository.
+"Head fork" should be your repository, and the "base fork" should be the iText official repository.
 * If we suggest changes then:
   * Make the required updates.
   * Fix up your commits if needed, with an interactive rebase.
@@ -111,7 +111,7 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
 
 We have guidelines on how our git commit messages should be formatted. This leads to **more
 readable messages** that are easy to follow when looking through the **project history**. But also,
-we use the git commit messages to **generate the iText 7 Community change log**.
+we use the git commit messages to **generate the iText Community change log**.
 
 These guidelines were taken from Chris Beams' blog post [How to Write a Git Commit Message][git-commit].
 

README.md

@@ -1,6 +1,6 @@
-**[pdfSweep][pdfSweep]** is an [iText 7][itext] add on.
+**[pdfSweep][pdfSweep]** is an [iText][itext] add on.
 
-This add on will allow you to easily construct e-Sweeps. As of yet, the only supported format is the ZUGFeRD standard. Support for other formats is on the way. Should you want to add support to a format then we invite you to take a look at our [Contribution Guidelines][contributing].
+This add on will allow you to easily redact PDF files. Redaction is the process of removing sensitive or confidential information. pdfSweep will remove this data entirely so that it won't be extractable anymore.
 
 The **pdfSweep Community** source code is hosted on [Github][github], where you can also [download the latest releases][latest].
 

pdfSweep.nuspec

@@ -3,14 +3,14 @@
   <metadata>
     <id>itext7.pdfsweep</id>
     <version>4.0.0-SNAPSHOT</version>
-    <title>iText 7 pdfSweep</title>
+    <title>iText pdfSweep</title>
     <authors>iText Software</authors>
     <owners>iText Software</owners>
     <licenseUrl>https://itextpdf.com/legal</licenseUrl>
     <projectUrl>https://itextpdf.com/</projectUrl>
     <icon>ITSC-avatar.png</icon>
     <requireLicenseAcceptance>true</requireLicenseAcceptance>
-    <description>pdfSweep is an iText 7 add-on that allows you to permanently remove or black out sensitive data from your PDF documents.</description>
+    <description>pdfSweep is an iText add-on that allows you to permanently remove or black out sensitive data from your PDF documents.</description>
     <summary />
     <releaseNotes>https://itextpdf.com/itext7release</releaseNotes>
     <copyright>Copyright (c) 1998-2023 iText Group NV</copyright>

port-hash

@@ -1 +1 @@
-27697b4faa7c3d5011cb9001fdccb97d662c5f49
+e2d1bf96f507643a2a652bd27be9fd17004a64c6