[#448] Update README and CHANGELOG.

CHANGELOG.md

@@ -1,32 +1,15 @@
 # Changelog
+
 All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## UNRELEASED
-
-### Added
-
-### Changed
-
-## UNRELEASED
-
-### Added
-
-### Changed
-
-#### First coordinated stream is required to close and update the catalog when doing parallel transfer #408
-
-Support for 'first stream closed last' semantics for NFSRods handling
-
-### Removed
-
 ## [4.3.3.0-RELEASE]
 
 #### First coordinated stream is required to close and update the catalog when doing parallel transfer #408
 
-Adjustments to close behavior for NFSRods in parallel transfer to close first stream last
+Adjustments to close behavior for NFSRODS in parallel transfer to close first stream last
 
 #### Additional options for file zipping/tarring
 

README.md

@@ -1,39 +1,26 @@
-# Project: Jargon-core API
-### Date: 12/15/2022
-### Release Version: 4.3.3.0-RELEASE
+# Jargon
 
-## News
-
-
-
-This is a maintenance and feature development release to support Metalnx, REST2, iDrop, NFS4J, and other efforts
-
-Please go to https://github.com/DICE-UNC/jargon for the latest news and info.
-
-=======
-
-Jargon-core consists of the following libraries
-
-* jargon-core - base libraries, implementation of the iRODS protocol
-* jargon-data-utils - additional functionality for dealing with iRODS data, such as building trees, storing information in iRODS on behalf of applications, and doing diffs between local and iRODS
-* jargon-user-tagging - code for using free tagging and other metadata metaphors on top of iRODS
-* jargon-user-profile - allows management of user profile and related configuration data in a user home directory
-* jargon-ticket - support for ticket processing
-* jargon-ruleservice - support for running and managing rules from interfaces
-* jargon-pool - initial implementation of commons-pool caching of iRODS agent connections.  This is initially for WebDav, and will be utilized as an option in REST and cloud browser.  Consider this code experimental
+The official iRODS client library for Java applications.
 
 ## Requirements
 
-* Jargon depends on Java 1.8+ with a current focus on testing/running under OpenJDK 11
-* Jargon is built using Apache Maven2, see POM for dependencies
-* Jargon supports iRODS current releases, it also maintains very reasonable backwards compatability to iRODS 3.3.1 however this is no longer actively tested
+- Jargon depends on Java 1.8+ with a current focus on testing/running under OpenJDK 11
+- Jargon is built using Apache Maven2, see POM for dependencies
+- Jargon supports iRODS current releases, it also maintains very reasonable backwards compatability to iRODS 3.3.1 however this is no longer actively tested
 
 ## Libraries
 
-Jargon-core uses Maven for dependency management.  See the pom.xml file for references to various dependencies.
+Jargon uses Maven for dependency management. See the pom.xml file for references to various dependencies.
 
-Note that the following bug and feature requests are logged in GitHub with related commit information https://github.com/DICE-UNC/jargon/issues
+This project consists of the following libraries:
+- jargon-core - Base libraries, implementation of the iRODS protocol
+- jargon-data-utils - Additional functionality for dealing with iRODS data, such as building trees, storing information in iRODS on behalf of applications, and doing diffs between local and iRODS
+- jargon-user-tagging - Code for using free tagging and other metadata metaphors on top of iRODS
+- jargon-user-profile - Allows management of user profile and related configuration data in a user home directory
+- jargon-ticket - Support for ticket processing
+- jargon-ruleservice - Support for running and managing rules from interfaces
+- jargon-pool - Initial implementation of commons-pool caching of iRODS agent connections. This is initially for WebDav, and will be utilized as an option in REST and cloud browser. Consider this code experimental
 
 ## Changes
 
-See CHANGELOG.md
+See [CHANGELOG](CHANGELOG.md) for updates.