Skip to content

Commit 260eece

Browse files
authored
Fixed some typos in COTR section
1 parent e8465f9 commit 260eece

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

finance/proposal-calls/cycle4/cycle4.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,11 +87,11 @@ Note that if your proposal has a longer Period of Performance than one year, fun
8787

8888
# COTRs
8989

90-
New this Cycle, all proposals will be assined a COTR (Contracting Officer's Technical Representative). This concept is borrowed from government funding agencies, although it is to be stressed that Astropy's goal is to make the COTR role as low-overhead as possible.
90+
New this Cycle, all proposals will be assigned a COTR (Contracting Officer's Technical Representative). This concept is borrowed from government funding agencies, although it is to be stressed that Astropy's goal is to make the COTR role as low-overhead as possible.
9191

9292
COTR's key responsibilities include:
9393

94-
* Technical expertise: They are experts in the contract's specific area, evaluating the contractor's performance with their technical knowledge.
94+
* Technical expertise: COTRs are experts in the contract's specific area, evaluating the contractor's performance with their technical knowledge.
9595
* Contract compliance: COTRs monitor and ensure the contractor follows contract terms, reviewing deliverables to meet expected Astropy community standards.
9696
* Performance evaluation: COTRs assess contractor performance, verifying the work meets contract expectations.
9797
* Issue resolution: COTRs play a role in resolving issues or disputes, collaborating with the finance committee, the Coordination Committee, and the broader Astropy Project.

0 commit comments

Comments
 (0)