brandeis-problemset (19jan19)

git-svn-id: svn://tug.org/texlive/trunk@49760 c570f23f-e606-0410-a88d-b1316a301751

7 files changed, 712 insertions, 938 deletions

diff --git a/Master/texmf-dist/doc/latex/brandeis-problemset/LICENSE.md b/Master/texmf-dist/doc/latex/brandeis-problemset/LICENSE.md
deleted file mode 100644
index 2fb2e74d8d7..00000000000
--- a/Master/texmf-dist/doc/latex/brandeis-problemset/LICENSE.md
+++ /dev/null
@@ -1,675 +0,0 @@
-### GNU GENERAL PUBLIC LICENSE
-
-Version 3, 29 June 2007
-
-Copyright (C) 2007 Free Software Foundation, Inc.
-<https://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this
-license document, but changing it is not allowed.
-
-### Preamble
-
-The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
-
-The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works. By contrast,
-the GNU General Public License is intended to guarantee your freedom
-to share and change all versions of a program--to make sure it remains
-free software for all its users. We, the Free Software Foundation, use
-the GNU General Public License for most of our software; it applies
-also to any other work released this way by its authors. You can apply
-it to your programs, too.
-
-When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights. Therefore, you
-have certain responsibilities if you distribute copies of the
-software, or if you modify it: responsibilities to respect the freedom
-of others.
-
-For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received. You must make sure that they, too, receive
-or can get the source code. And you must show them these terms so they
-know their rights.
-
-Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-
-For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software. For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-
-Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the
-manufacturer can do so. This is fundamentally incompatible with the
-aim of protecting users' freedom to change the software. The
-systematic pattern of such abuse occurs in the area of products for
-individuals to use, which is precisely where it is most unacceptable.
-Therefore, we have designed this version of the GPL to prohibit the
-practice for those products. If such problems arise substantially in
-other domains, we stand ready to extend this provision to those
-domains in future versions of the GPL, as needed to protect the
-freedom of users.
-
-Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish
-to avoid the special danger that patents applied to a free program
-could make it effectively proprietary. To prevent this, the GPL
-assures that patents cannot be used to render the program non-free.
-
-The precise terms and conditions for copying, distribution and
-modification follow.
-
-### TERMS AND CONDITIONS
-
-#### 0. Definitions.
-
-"This License" refers to version 3 of the GNU General Public License.
-
-"Copyright" also means copyright-like laws that apply to other kinds
-of works, such as semiconductor masks.
-
-"The Program" refers to any copyrightable work licensed under this
-License. Each licensee is addressed as "you". "Licensees" and
-"recipients" may be individuals or organizations.
-
-To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of
-an exact copy. The resulting work is called a "modified version" of
-the earlier work or a work "based on" the earlier work.
-
-A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy. Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user
-through a computer network, with no transfer of a copy, is not
-conveying.
-
-An interactive user interface displays "Appropriate Legal Notices" to
-the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License. If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-#### 1. Source Code.
-
-The "source code" for a work means the preferred form of the work for
-making modifications to it. "Object code" means any non-source form of
-a work.
-
-A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form. A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities. However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-The Corresponding Source need not include anything that users can
-regenerate automatically from other parts of the Corresponding Source.
-
-The Corresponding Source for a work in source code form is that same
-work.
-
-#### 2. Basic Permissions.
-
-All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met. This License explicitly affirms your unlimited
-permission to run the unmodified Program. The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-You may make, run and propagate covered works that you do not convey,
-without conditions so long as your license otherwise remains in force.
-You may convey covered works to others for the sole purpose of having
-them make modifications exclusively for you, or provide you with
-facilities for running those works, provided that you comply with the
-terms of this License in conveying all material for which you do not
-control copyright. Those thus making or running the covered works for
-you must do so exclusively on your behalf, under your direction and
-control, on terms that prohibit them from making any copies of your
-copyrighted material outside their relationship with you.
-
-Conveying under any other circumstances is permitted solely under the
-conditions stated below. Sublicensing is not allowed; section 10 makes
-it unnecessary.
-
-#### 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such
-circumvention is effected by exercising rights under this License with
-respect to the covered work, and you disclaim any intention to limit
-operation or modification of the work as a means of enforcing, against
-the work's users, your or third parties' legal rights to forbid
-circumvention of technological measures.
-
-#### 4. Conveying Verbatim Copies.
-
-You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-#### 5. Conveying Modified Source Versions.
-
-You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these
-conditions:
-
--   a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
--   b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under
-    section 7. This requirement modifies the requirement in section 4
-    to "keep intact all notices".
--   c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy. This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged. This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
--   d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-#### 6. Conveying Non-Source Forms.
-
-You may convey a covered work in object code form under the terms of
-sections 4 and 5, provided that you also convey the machine-readable
-Corresponding Source under the terms of this License, in one of these
-ways:
-
--   a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
--   b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the Corresponding
-    Source from a network server at no charge.
--   c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source. This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
--   d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge. You need not require recipients to copy the
-    Corresponding Source along with the object code. If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source. Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
--   e) Convey the object code using peer-to-peer transmission,
-    provided you inform other peers where the object code and
-    Corresponding Source of the work are being offered to the general
-    public at no charge under subsection 6d.
-
-A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal,
-family, or household purposes, or (2) anything designed or sold for
-incorporation into a dwelling. In determining whether a product is a
-consumer product, doubtful cases shall be resolved in favor of
-coverage. For a particular product received by a particular user,
-"normally used" refers to a typical or common use of that class of
-product, regardless of the status of the particular user or of the way
-in which the particular user actually uses, or expects or is expected
-to use, the product. A product is a consumer product regardless of
-whether the product has substantial commercial, industrial or
-non-consumer uses, unless such uses represent the only significant
-mode of use of the product.
-
-"Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to
-install and execute modified versions of a covered work in that User
-Product from a modified version of its Corresponding Source. The
-information must suffice to ensure that the continued functioning of
-the modified object code is in no case prevented or interfered with
-solely because modification has been made.
-
-If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information. But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or
-updates for a work that has been modified or installed by the
-recipient, or for the User Product in which it has been modified or
-installed. Access to a network may be denied when the modification
-itself materially and adversely affects the operation of the network
-or violates the rules and protocols for communication across the
-network.
-
-Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-#### 7. Additional Terms.
-
-"Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law. If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it. (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.) You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders
-of that material) supplement the terms of this License with terms:
-
--   a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
--   b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
--   c) Prohibiting misrepresentation of the origin of that material,
-    or requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
--   d) Limiting the use for publicity purposes of names of licensors
-    or authors of the material; or
--   e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
--   f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions
-    of it) with contractual assumptions of liability to the recipient,
-    for any liability that these contractual assumptions directly
-    impose on those licensors and authors.
-
-All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10. If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term. If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions; the
-above requirements apply either way.
-
-#### 8. Termination.
-
-You may not propagate or modify a covered work except as expressly
-provided under this License. Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-However, if you cease all violation of this License, then your license
-from a particular copyright holder is reinstated (a) provisionally,
-unless and until the copyright holder explicitly and finally
-terminates your license, and (b) permanently, if the copyright holder
-fails to notify you of the violation by some reasonable means prior to
-60 days after the cessation.
-
-Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License. If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-#### 9. Acceptance Not Required for Having Copies.
-
-You are not required to accept this License in order to receive or run
-a copy of the Program. Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance. However,
-nothing other than this License grants you permission to propagate or
-modify any covered work. These actions infringe copyright if you do
-not accept this License. Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-#### 10. Automatic Licensing of Downstream Recipients.
-
-Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License. You are not responsible
-for enforcing compliance by third parties with this License.
-
-An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations. If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License. For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-#### 11. Patents.
-
-A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The
-work thus licensed is called the contributor's "contributor version".
-
-A contributor's "essential patent claims" are all patent claims owned
-or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version. For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement). To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients. "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-A patent license is "discriminatory" if it does not include within the
-scope of its coverage, prohibits the exercise of, or is conditioned on
-the non-exercise of one or more of the rights that are specifically
-granted under this License. You may not convey a covered work if you
-are a party to an arrangement with a third party that is in the
-business of distributing software, under which you make payment to the
-third party based on the extent of your activity of conveying the
-work, and under which the third party grants, to any of the parties
-who would receive the covered work from you, a discriminatory patent
-license (a) in connection with copies of the covered work conveyed by
-you (or copies made from those copies), or (b) primarily for and in
-connection with specific products or compilations that contain the
-covered work, unless you entered into that arrangement, or that patent
-license was granted, prior to 28 March 2007.
-
-Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-#### 12. No Surrender of Others' Freedom.
-
-If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under
-this License and any other pertinent obligations, then as a
-consequence you may not convey it at all. For example, if you agree to
-terms that obligate you to collect a royalty for further conveying
-from those to whom you convey the Program, the only way you could
-satisfy both those terms and this License would be to refrain entirely
-from conveying the Program.
-
-#### 13. Use with the GNU Affero General Public License.
-
-Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
-combined work, and to convey the resulting work. The terms of this
-License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
-
-#### 14. Revised Versions of this License.
-
-The Free Software Foundation may publish revised and/or new versions
-of the GNU General Public License from time to time. Such new versions
-will be similar in spirit to the present version, but may differ in
-detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies that a certain numbered version of the GNU General Public
-License "or any later version" applies to it, you have the option of
-following the terms and conditions either of that numbered version or
-of any later version published by the Free Software Foundation. If the
-Program does not specify a version number of the GNU General Public
-License, you may choose any version ever published by the Free
-Software Foundation.
-
-If the Program specifies that a proxy can decide which future versions
-of the GNU General Public License can be used, that proxy's public
-statement of acceptance of a version permanently authorizes you to
-choose that version for the Program.
-
-Later license versions may give you additional or different
-permissions. However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-#### 15. Disclaimer of Warranty.
-
-THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
-LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
-PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
-DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
-CORRECTION.
-
-#### 16. Limitation of Liability.
-
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR
-CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT
-NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
-LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
-TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
-PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-#### 17. Interpretation of Sections 15 and 16.
-
-If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-END OF TERMS AND CONDITIONS
-
-### How to Apply These Terms to Your New Programs
-
-If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these
-terms.
-
-To do so, attach the following notices to the program. It is safest to
-attach them to the start of each source file to most effectively state
-the exclusion of warranty; and each file should have at least the
-"copyright" line and a pointer to where the full notice is found.
-
-        <one line to give the program's name and a brief idea of what it does.>
-        Copyright (C) <year>  <name of author>
-
-        This program is free software: you can redistribute it and/or modify
-        it under the terms of the GNU General Public License as published by
-        the Free Software Foundation, either version 3 of the License, or
-        (at your option) any later version.
-
-        This program is distributed in the hope that it will be useful,
-        but WITHOUT ANY WARRANTY; without even the implied warranty of
-        MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-        GNU General Public License for more details.
-
-        You should have received a copy of the GNU General Public License
-        along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper
-mail.
-
-If the program does terminal interaction, make it output a short
-notice like this when it starts in an interactive mode:
-
-        <program>  Copyright (C) <year>  <name of author>
-        This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-        This is free software, and you are welcome to redistribute it
-        under certain conditions; type `show c' for details.
-
-The hypothetical commands \`show w' and \`show c' should show the
-appropriate parts of the General Public License. Of course, your
-program's commands might be different; for a GUI interface, you would
-use an "about box".
-
-You should also get your employer (if you work as a programmer) or
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. For more information on this, and how to apply and follow
-the GNU GPL, see <https://www.gnu.org/licenses/>.
-
-The GNU General Public License does not permit incorporating your
-program into proprietary programs. If your program is a subroutine
-library, you may consider it more useful to permit linking proprietary
-applications with the library. If this is what you want to do, use the
-GNU Lesser General Public License instead of this License. But first,
-please read <https://www.gnu.org/licenses/why-not-lgpl.html>.
diff --git a/Master/texmf-dist/doc/latex/brandeis-problemset/LICENSE.txt b/Master/texmf-dist/doc/latex/brandeis-problemset/LICENSE.txt
new file mode 100644
index 00000000000..22443139013
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/brandeis-problemset/LICENSE.txt
@@ -0,0 +1,416 @@
+The LaTeX Project Public License
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+
+LPPL Version 1.3c  2008-05-04
+
+Copyright 1999 2002-2008 LaTeX3 Project
+    Everyone is allowed to distribute verbatim copies of this
+    license document, but modification of it is not allowed.
+
+
+PREAMBLE
+========
+
+The LaTeX Project Public License (LPPL) is the primary license under
+which the LaTeX kernel and the base LaTeX packages are distributed.
+
+You may use this license for any work of which you hold the copyright
+and which you wish to distribute.  This license may be particularly
+suitable if your work is TeX-related (such as a LaTeX package), but 
+it is written in such a way that you can use it even if your work is 
+unrelated to TeX.
+
+The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+below, gives instructions, examples, and recommendations for authors
+who are considering distributing their works under this license.
+
+This license gives conditions under which a work may be distributed
+and modified, as well as conditions under which modified versions of
+that work may be distributed.
+
+We, the LaTeX3 Project, believe that the conditions below give you
+the freedom to make and distribute modified versions of your work
+that conform with whatever technical specifications you wish while
+maintaining the availability, integrity, and reliability of
+that work.  If you do not see how to achieve your goal while
+meeting these conditions, then read the document `cfgguide.tex'
+and `modguide.tex' in the base LaTeX distribution for suggestions.
+
+
+DEFINITIONS
+===========
+
+In this license document the following terms are used:
+
+   `Work'
+    Any work being distributed under this License.
+    
+   `Derived Work'
+    Any work that under any applicable law is derived from the Work.
+
+   `Modification' 
+    Any procedure that produces a Derived Work under any applicable
+    law -- for example, the production of a file containing an
+    original file associated with the Work or a significant portion of
+    such a file, either verbatim or with modifications and/or
+    translated into another language.
+
+   `Modify'
+    To apply any procedure that produces a Derived Work under any
+    applicable law.
+    
+   `Distribution'
+    Making copies of the Work available from one person to another, in
+    whole or in part.  Distribution includes (but is not limited to)
+    making any electronic components of the Work accessible by
+    file transfer protocols such as FTP or HTTP or by shared file
+    systems such as Sun's Network File System (NFS).
+
+   `Compiled Work'
+    A version of the Work that has been processed into a form where it
+    is directly usable on a computer system.  This processing may
+    include using installation facilities provided by the Work,
+    transformations of the Work, copying of components of the Work, or
+    other activities.  Note that modification of any installation
+    facilities provided by the Work constitutes modification of the Work.
+
+   `Current Maintainer'
+    A person or persons nominated as such within the Work.  If there is
+    no such explicit nomination then it is the `Copyright Holder' under
+    any applicable law.
+
+   `Base Interpreter' 
+    A program or process that is normally needed for running or
+    interpreting a part or the whole of the Work.    
+
+    A Base Interpreter may depend on external components but these
+    are not considered part of the Base Interpreter provided that each
+    external component clearly identifies itself whenever it is used
+    interactively.  Unless explicitly specified when applying the
+    license to the Work, the only applicable Base Interpreter is a
+    `LaTeX-Format' or in the case of files belonging to the 
+    `LaTeX-format' a program implementing the `TeX language'.
+
+
+
+CONDITIONS ON DISTRIBUTION AND MODIFICATION
+===========================================
+
+1.  Activities other than distribution and/or modification of the Work
+are not covered by this license; they are outside its scope.  In
+particular, the act of running the Work is not restricted and no
+requirements are made concerning any offers of support for the Work.
+
+2.  You may distribute a complete, unmodified copy of the Work as you
+received it.  Distribution of only part of the Work is considered
+modification of the Work, and no right to distribute such a Derived
+Work may be assumed under the terms of this clause.
+
+3.  You may distribute a Compiled Work that has been generated from a
+complete, unmodified copy of the Work as distributed under Clause 2
+above, as long as that Compiled Work is distributed in such a way that
+the recipients may install the Compiled Work on their system exactly
+as it would have been installed if they generated a Compiled Work
+directly from the Work.
+
+4.  If you are the Current Maintainer of the Work, you may, without
+restriction, modify the Work, thus creating a Derived Work.  You may
+also distribute the Derived Work without restriction, including
+Compiled Works generated from the Derived Work.  Derived Works
+distributed in this manner by the Current Maintainer are considered to
+be updated versions of the Work.
+
+5.  If you are not the Current Maintainer of the Work, you may modify
+your copy of the Work, thus creating a Derived Work based on the Work,
+and compile this Derived Work, thus creating a Compiled Work based on
+the Derived Work.
+
+6.  If you are not the Current Maintainer of the Work, you may
+distribute a Derived Work provided the following conditions are met
+for every component of the Work unless that component clearly states
+in the copyright notice that it is exempt from that condition.  Only
+the Current Maintainer is allowed to add such statements of exemption 
+to a component of the Work. 
+
+  a. If a component of this Derived Work can be a direct replacement
+     for a component of the Work when that component is used with the
+     Base Interpreter, then, wherever this component of the Work
+     identifies itself to the user when used interactively with that
+     Base Interpreter, the replacement component of this Derived Work
+     clearly and unambiguously identifies itself as a modified version
+     of this component to the user when used interactively with that
+     Base Interpreter.
+     
+  b. Every component of the Derived Work contains prominent notices
+     detailing the nature of the changes to that component, or a
+     prominent reference to another file that is distributed as part
+     of the Derived Work and that contains a complete and accurate log
+     of the changes.
+  
+  c. No information in the Derived Work implies that any persons,
+     including (but not limited to) the authors of the original version
+     of the Work, provide any support, including (but not limited to)
+     the reporting and handling of errors, to recipients of the
+     Derived Work unless those persons have stated explicitly that
+     they do provide such support for the Derived Work.
+
+  d. You distribute at least one of the following with the Derived Work:
+
+       1. A complete, unmodified copy of the Work; 
+          if your distribution of a modified component is made by
+          offering access to copy the modified component from a
+          designated place, then offering equivalent access to copy
+          the Work from the same or some similar place meets this
+          condition, even though third parties are not compelled to
+          copy the Work along with the modified component;
+
+       2. Information that is sufficient to obtain a complete,
+          unmodified copy of the Work.
+
+7.  If you are not the Current Maintainer of the Work, you may
+distribute a Compiled Work generated from a Derived Work, as long as
+the Derived Work is distributed to all recipients of the Compiled
+Work, and as long as the conditions of Clause 6, above, are met with
+regard to the Derived Work.
+
+8.  The conditions above are not intended to prohibit, and hence do not
+apply to, the modification, by any method, of any component so that it
+becomes identical to an updated version of that component of the Work as
+it is distributed by the Current Maintainer under Clause 4, above.
+
+9.  Distribution of the Work or any Derived Work in an alternative
+format, where the Work or that Derived Work (in whole or in part) is
+then produced by applying some process to that format, does not relax or
+nullify any sections of this license as they pertain to the results of
+applying that process.
+     
+10. a. A Derived Work may be distributed under a different license
+       provided that license itself honors the conditions listed in
+       Clause 6 above, in regard to the Work, though it does not have
+       to honor the rest of the conditions in this license.
+      
+    b. If a Derived Work is distributed under a different license, that
+       Derived Work must provide sufficient documentation as part of
+       itself to allow each recipient of that Derived Work to honor the 
+       restrictions in Clause 6 above, concerning changes from the Work.
+
+11. This license places no restrictions on works that are unrelated to
+the Work, nor does this license place any restrictions on aggregating
+such works with the Work by any means.
+
+12.  Nothing in this license is intended to, or may be used to, prevent
+complete compliance by all parties with all applicable laws.
+
+
+NO WARRANTY
+===========
+
+There is no warranty for the Work.  Except when otherwise stated in
+writing, the Copyright Holder provides the Work `as is', without
+warranty of any kind, either expressed or implied, including, but not
+limited to, the implied warranties of merchantability and fitness for a
+particular purpose.  The entire risk as to the quality and performance
+of the Work is with you.  Should the Work prove defective, you assume
+the cost of all necessary servicing, repair, or correction.
+
+In no event unless required by applicable law or agreed to in writing
+will The Copyright Holder, or any author named in the components of the
+Work, or any other party who may distribute and/or modify the Work as
+permitted above, be liable to you for damages, including any general,
+special, incidental or consequential damages arising out of any use of
+the Work or out of inability to use the Work (including, but not limited
+to, loss of data, data being rendered inaccurate, or losses sustained by
+anyone as a result of any failure of the Work to operate with any other
+programs), even if the Copyright Holder or said author or said other
+party has been advised of the possibility of such damages.
+
+
+MAINTENANCE OF THE WORK
+=======================
+
+The Work has the status `author-maintained' if the Copyright Holder
+explicitly and prominently states near the primary copyright notice in
+the Work that the Work can only be maintained by the Copyright Holder
+or simply that it is `author-maintained'.
+
+The Work has the status `maintained' if there is a Current Maintainer
+who has indicated in the Work that they are willing to receive error
+reports for the Work (for example, by supplying a valid e-mail
+address). It is not required for the Current Maintainer to acknowledge
+or act upon these error reports.
+
+The Work changes from status `maintained' to `unmaintained' if there
+is no Current Maintainer, or the person stated to be Current
+Maintainer of the work cannot be reached through the indicated means
+of communication for a period of six months, and there are no other
+significant signs of active maintenance.
+
+You can become the Current Maintainer of the Work by agreement with
+any existing Current Maintainer to take over this role.
+
+If the Work is unmaintained, you can become the Current Maintainer of
+the Work through the following steps:
+
+ 1.  Make a reasonable attempt to trace the Current Maintainer (and
+     the Copyright Holder, if the two differ) through the means of
+     an Internet or similar search.
+
+ 2.  If this search is successful, then enquire whether the Work
+     is still maintained.
+
+  a. If it is being maintained, then ask the Current Maintainer
+     to update their communication data within one month.
+     
+  b. If the search is unsuccessful or no action to resume active
+     maintenance is taken by the Current Maintainer, then announce
+     within the pertinent community your intention to take over
+     maintenance.  (If the Work is a LaTeX work, this could be
+     done, for example, by posting to comp.text.tex.)
+
+ 3a. If the Current Maintainer is reachable and agrees to pass
+     maintenance of the Work to you, then this takes effect
+     immediately upon announcement.
+     
+  b. If the Current Maintainer is not reachable and the Copyright
+     Holder agrees that maintenance of the Work be passed to you,
+     then this takes effect immediately upon announcement.  
+    
+ 4.  If you make an `intention announcement' as described in 2b. above
+     and after three months your intention is challenged neither by
+     the Current Maintainer nor by the Copyright Holder nor by other
+     people, then you may arrange for the Work to be changed so as
+     to name you as the (new) Current Maintainer.
+     
+ 5.  If the previously unreachable Current Maintainer becomes
+     reachable once more within three months of a change completed
+     under the terms of 3b) or 4), then that Current Maintainer must
+     become or remain the Current Maintainer upon request provided
+     they then update their communication data within one month.
+
+A change in the Current Maintainer does not, of itself, alter the fact
+that the Work is distributed under the LPPL license.
+
+If you become the Current Maintainer of the Work, you should
+immediately provide, within the Work, a prominent and unambiguous
+statement of your status as Current Maintainer.  You should also
+announce your new status to the same pertinent community as
+in 2b) above.
+
+
+WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+======================================================
+
+This section contains important instructions, examples, and
+recommendations for authors who are considering distributing their
+works under this license.  These authors are addressed as `you' in
+this section.
+
+Choosing This License or Another License
+----------------------------------------
+
+If for any part of your work you want or need to use *distribution*
+conditions that differ significantly from those in this license, then
+do not refer to this license anywhere in your work but, instead,
+distribute your work under a different license.  You may use the text
+of this license as a model for your own license, but your license
+should not refer to the LPPL or otherwise give the impression that
+your work is distributed under the LPPL.
+
+The document `modguide.tex' in the base LaTeX distribution explains
+the motivation behind the conditions of this license.  It explains,
+for example, why distributing LaTeX under the GNU General Public
+License (GPL) was considered inappropriate.  Even if your work is
+unrelated to LaTeX, the discussion in `modguide.tex' may still be
+relevant, and authors intending to distribute their works under any
+license are encouraged to read it.
+
+A Recommendation on Modification Without Distribution
+-----------------------------------------------------
+
+It is wise never to modify a component of the Work, even for your own
+personal use, without also meeting the above conditions for
+distributing the modified component.  While you might intend that such
+modifications will never be distributed, often this will happen by
+accident -- you may forget that you have modified that component; or
+it may not occur to you when allowing others to access the modified
+version that you are thus distributing it and violating the conditions
+of this license in ways that could have legal implications and, worse,
+cause problems for the community.  It is therefore usually in your
+best interest to keep your copy of the Work identical with the public
+one.  Many works provide ways to control the behavior of that work
+without altering any of its licensed components.
+
+How to Use This License
+-----------------------
+
+To use this license, place in each of the components of your work both
+an explicit copyright notice including your name and the year the work
+was authored and/or last substantially modified.  Include also a
+statement that the distribution and/or modification of that
+component is constrained by the conditions in this license.
+
+Here is an example of such a notice and statement:
+
+  %% pig.dtx
+  %% Copyright 2005 M. Y. Name
+  %
+  % This work may be distributed and/or modified under the
+  % conditions of the LaTeX Project Public License, either version 1.3
+  % of this license or (at your option) any later version.
+  % The latest version of this license is in
+  %   http://www.latex-project.org/lppl.txt
+  % and version 1.3 or later is part of all distributions of LaTeX
+  % version 2005/12/01 or later.
+  %
+  % This work has the LPPL maintenance status `maintained'.
+  % 
+  % The Current Maintainer of this work is M. Y. Name.
+  %
+  % This work consists of the files pig.dtx and pig.ins
+  % and the derived file pig.sty.
+
+Given such a notice and statement in a file, the conditions
+given in this license document would apply, with the `Work' referring
+to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+referring to any `LaTeX-Format', and both `Copyright Holder' and
+`Current Maintainer' referring to the person `M. Y. Name'.
+
+If you do not want the Maintenance section of LPPL to apply to your
+Work, change `maintained' above into `author-maintained'.  
+However, we recommend that you use `maintained', as the Maintenance
+section was added in order to ensure that your Work remains useful to
+the community even when you can no longer maintain and support it
+yourself.
+
+Derived Works That Are Not Replacements
+---------------------------------------
+
+Several clauses of the LPPL specify means to provide reliability and
+stability for the user community. They therefore concern themselves
+with the case that a Derived Work is intended to be used as a
+(compatible or incompatible) replacement of the original Work. If
+this is not the case (e.g., if a few lines of code are reused for a
+completely different task), then clauses 6b and 6d shall not apply.
+
+
+Important Recommendations
+-------------------------
+
+ Defining What Constitutes the Work
+
+   The LPPL requires that distributions of the Work contain all the
+   files of the Work.  It is therefore important that you provide a
+   way for the licensee to determine which files constitute the Work.
+   This could, for example, be achieved by explicitly listing all the
+   files of the Work near the copyright notice of each file or by
+   using a line such as:
+
+    % This work consists of all files listed in manifest.txt.
+   
+   in that place.  In the absence of an unequivocal list it might be
+   impossible for the licensee to determine what is considered by you
+   to comprise the Work and, in such a case, the licensee would be
+   entitled to make reasonable conjectures as to which files comprise
+   the Work.
+
diff --git a/Master/texmf-dist/doc/latex/brandeis-problemset/README.md b/Master/texmf-dist/doc/latex/brandeis-problemset/README.md
index 0a960562919..00af4ab0311 100644
--- a/Master/texmf-dist/doc/latex/brandeis-problemset/README.md
+++ b/Master/texmf-dist/doc/latex/brandeis-problemset/README.md
@@ -10,9 +10,7 @@ File                        | Description
 brandeis-problemset.cls     | The brandeis-problemset document class
 brandeis-problemset.pdf     | Documentation (English)
 brandeis-problemset.tex     | Documentation source
-brandeis-problemset-doc.sty | Documentation styles
+example.tex                 | Example problem set
+example.pdf                 | Example problem set
 README.md                   | This file
-
-## License
-
-GNU GPLv3; see `LICENSE.md`
+LICENSE.txt                 | LPPL 1.3c
diff --git a/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset-doc.sty b/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset-doc.sty
deleted file mode 100644
index d9553a99786..00000000000
--- a/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset-doc.sty
+++ /dev/null
@@ -1,34 +0,0 @@
-\usepackage{hypdoc}
-\usepackage[
-	loadHyperref=false,
-	createIndexEntries=false
-]{doctools}
-
-\PageIndex
-\EnableCrossrefs
-
-\usepackage{textcomp} % needed for listings
-\usepackage{xparse}
-\usepackage{hologo} % xetex, etc. logos
-\usepackage{xkeyval}
-\usepackage{cprotect}
-\usepackage{changelog}
-
-\newcommand{\email}[1]{\href{mailto:#1}{\texttt{#1}}}
-\newcommand{\https}[1]{\href{https://#1}{\texttt{#1}}}
-\newcommand{\bps}{\ltxclass{brandeis-problemset}}
-\newcommand{\cosi}[1]{\textsc{cosi}~#1}
-\newcommand{\todo}[1]{\begin{itemize}\item[\textbf{To-do:}] #1 \end{itemize}}
-\newcommand{\note}[1]{\begin{itemize}\item[\textbf{Note:}] #1 \end{itemize}}
-\newcommand{\ctan}[1]{\href{https://ctan.org/pkg/#1}{\package{#1}}}
-\NewExpandableDocumentCommand{\Th}{O{l} m}
-	{\multicolumn{1}{#1}{\textbf{#2}}}
-\newcommand{\fontspecok}{\hologo{XeLaTeX} or \hologo{LuaTeX}}
-\newcommand{\ext}[1]{\texttt{.#1}}
-\newcommand{\filename}[1]{\texttt{#1}}
-
-% definition copied from doc package \DescribeMacro
-\lstnewenvironment{latexfile}[1]
-	{\lstset{style=lstDemoStyleLaTeXCode}%
-	}
-	{}
diff --git a/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset.pdf b/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset.pdf
index deaa744c6a7..bbf33124c3b 100644
--- a/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset.pdf
+++ b/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset.pdf
diff --git a/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset.tex b/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset.tex
index 0f1e934a9f3..6e14d4b37c1 100644
--- a/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset.tex
+++ b/Master/texmf-dist/doc/latex/brandeis-problemset/brandeis-problemset.tex
@@ -1,27 +1,51 @@
-\documentclass{ltxdoc}
-\usepackage{brandeis-problemset-doc}
+\documentclass{ltxguidex}
+\usepackage{textcomp} % needed for listings
+\usepackage{hologo} % xetex, etc. logos
+\usepackage{changelog}
+\newcommand{\bps}{\ltxclass{brandeis-problemset}}
+\newcommand{\fontspecok}{\hologo{XeLaTeX} or \hologo{LuaTeX}}
+\newcommand{\cosi}[1]{\textsc{cosi}~#1}
+\newnotice{todo}{To-do}
+
+\usepackage{fontspec}
+\setmainfont{Tiempos Text}
+\usepackage{FiraSans}
+\usepackage{FiraMono}
+
+\lstnewenvironment{latexfile}[1]
+	{\lstset{
+		language=[LaTeX]TeX,
+		numbers=none,
+	}}
+	{}
+
 \author{Rebecca Turner\thanks{Brandeis University; \email{rebeccaturner@brandeis.edu}}}
 \title{The \bps\ Document Class}
-\date{2019-01-03}
+\date{2019/01/19}
 \begin{document}
 \maketitle
 \begin{abstract}
 
 	Brandeis University's computer science (``\textsc{cosi}'') courses
 	often assign ``problem sets'' which require fairly rigorous
-	formatting. The \bps\ document class, which extends
-	\ltxclass{article}, provides a simple way to typeset these problem
-	sets in \LaTeX.
+	formatting. The \ctan{brandeis-problemset} document class, which
+	extends \ltxclass{article}, provides a simple way to typeset these
+	problem sets in \LaTeX.
 
 	Although \bps\ is compatible with all \LaTeX\ flavors, \fontspecok\
 	is recommended for \ctan{fontspec} support.
 
 \end{abstract}
 
-\note{The \bps\ document class should be considered experimental; the only
-stable \textsc{api} is that of the \env{problem} environment.}
-\note{Browse the sources, contribute, or complain at \\
-	\https{github.com/9999years/brandeis-problemset}}
+\begin{note}
+	The \bps\ document class should be considered experimental; the only
+	stable \textsc{api} is that of the |problem| environment.
+\end{note}
+
+\begin{note}
+	Browse the sources, contribute, or complain at \\
+	\https{github.com/9999years/brandeis-problemset}
+\end{note}
 
 \tableofcontents
 \vfill
@@ -30,7 +54,7 @@ stable \textsc{api} is that of the \env{problem} environment.}
 \section{Default behavior}
 
 \bps\ provides packages and well-formatted constructs (notably the
-\env{problem} environment) for problem-set writers. \bps\ will always render
+|problem| environment) for problem-set writers. \bps\ will always render
 its body copy as a Times variant (\ctan{stix} for plain \LaTeX\ or
 \ctan{xits} with \fontspecok) and always contains a useful header (which
 contains the page number, author's name, course, instructor, and assignment
@@ -40,19 +64,19 @@ due date).
 
 \begin{enumerate}
 \item \ctan{hyperref}, for a nicely-linked table of contents;
-	\cs{href}|{url}{label}|.
+	|\href||{url}{label}|.
 \item \ctan{listings}, for verbatim code listings (including the
-	\env{assembly}, \env{java}, and \env{pseudocode} environments).
+	|assembly|, |java|, and |pseudocode| environments).
 \item \ctan{xcolor}, for gray line numbers in code listings (and perhaps
-	colored listings in the future); e.g.\ \cs{color}|{gray}|.
+	colored listings in the future); e.g.\ |\color||{gray}|.
 \item \ctan{enumitem} for better control over the margins and spacing of
-	the \env{enumerate}, \env{itemize}, and \env{description}
+	the |enumerate|, |itemize|, and |description|
 	environments.
 \item Math packages: \begin{enumerate}
 	\item \ctan{amsmath} for tons of useful math commands, including
-		\cs{text}, \cs{intertext}, and \cs{boxed} as well as the \env{bmatrix},
-		\env{multiline}, \env{gather}, \env{align}, and
-		\env{alignat} environments. See
+		|\text|, |\intertext|, and |\boxed| as well as the |bmatrix|,
+		|multiline|, |gather|, |align|, and
+		|alignat| environments. See
 		\href{http://texdoc.net/texmf-dist/doc/latex/amsmath/amsldoc.pdf}{``User's
 		Guide for the \package{amsmath} Package''} for a more
 		complete listing.
@@ -60,7 +84,7 @@ due date).
 \end{enumerate}
 \item Table packages: \begin{enumerate}
 	\item \ctan{multirow} for cells spanning multiple rows.
-	\item \ctan{booktabs} for good-by-default tables and the \cs{cline}
+	\item \ctan{booktabs} for good-by-default tables and the |\cline|
 		macro.
 	\item \ctan{tabu}, the best table package with dynamically resizable
 		columns, easy creation of new column types, and more.
@@ -73,77 +97,80 @@ due date).
 
 Class options are limited to configuration options which require the loading
 of fonts or other packages; ``string'' settings like the assignment's due
-date are configured either with the \cs{problemsetsetup} command or the
+date are configured either with the |\problemsetsetup| command or the
 commands described in section~\ref{sss:configcommands}.
 
-\begin{Optionlist}
-	gantt &  Load packages for the \env{ganttschedule} environment \\
-	scheme & Define the \texttt{scheme} language for the \ctan{listings}
-		package as well as the \env{scheme} shorthand environment. \\
-	antonella & Use Dr.\ Antonella DiLillio's preferred styles (Courier
-		for code) \\
-	solutions & Include \env{solution} environments in compiled
-		document. \\
-\end{Optionlist}
+\begin{keys}
+	\key{gantt} Load packages for the |ganttschedule| environment.
+	\key{scheme} Define the |scheme| language for the \ctan{listings}
+		package as well as the |scheme| shorthand environment.
+	\key{antonella} Use Dr.\ Antonella DiLillio's preferred styles (Courier
+		for code)
+	\key{solutions} Include |solution| environments in compiled
+		document.
+\end{keys}
 
 \subsection{Setting options after loading \bps}
 
-\begin{macro}{\problemsetsetup}\marg{options}\AfterLastParam Sets global
-\bps\ options; see table~\ref{tab:problemset-options} for a list of valid
-options.
-
-\begin{table}[h]
-	\centering
-	\caption{Options for \cs{problemsetsetup}}
-	\label{tab:problemset-options}
-	\begin{Optionlist}
-	course & Course name in full. \\
-	coursenumber & Course name shorthand; use \texttt{21a} for
-		``\cosi{21a}''. \\
-	assignment & Assignment name in full. \\
-	number & Assignment name shorthand; use \texttt{3} for ``Problem Set
-		3''. \\
-	duedate & Due date, e.g.\ \texttt{2018-10-18}; not parsed at all,
-		but
-		\href{https://en.wikipedia.org/wiki/ISO_8601}{\textsc{iso}
-		8601 dates} are highly recommended. \\
-	instructor & Course instructor. \\
-	codefont & With \fontspecok, pass the given font to \cs{setmonofont}
-		and enable Unicode shortcuts for the \env{pseudocode}
-		environment. (If you need to specify options to
-		\cs{setmonofont}, use \cs{setcodefont}.) \\
-	gantt & Load packages for the \env{ganttschedule} environment \\
-	antonella & True/false (default: false; if no value specified,
-		assumes true); use Dr.\ Antonella DiLillio's preferred
-		styles (Courier for code) \\
-	solutions & Include \env{solution} environments in compiled
-		document. \\
-	\end{Optionlist}
-\end{table}
-\end{macro}
+\begin{desc}
+|\problemsetsetup{<options>}|
+\end{desc}
+Sets global \bps\ options.
+
+\begin{keys}
+\key{course}[\m{course name}]
+	Course name in full.
+\key{coursenumber}[\m{course number}]
+	Course name shorthand; use \texttt{21a} for ``\cosi{21a}''.
+\key{assignment}[\m{assignment name}]
+	Assignment name in full.
+\key{number}[\m{problem set number}]
+	Assignment name shorthand; use \texttt{3} for ``Problem Set 3''.
+\key{duedate}[\m{due date}]
+	Due date, e.g.\ \texttt{2018-10-18}; not parsed at all, but
+	\href{https://en.wikipedia.org/wiki/ISO_8601}{\textsc{iso} 8601
+	dates} are highly recommended.
+\key{instructor}[\m{course instructor}]
+	Course instructor.
+\key{author}[\m{your name}]
+	Alternate interface for the |\author| command.
+\key{date}[\m{document date}]
+	Alternate interface for the |\date| command.
+\key{codefont}[\m{fontspec font name}]
+	With \fontspecok, pass the given font to |\setmonofont| and enable
+	Unicode shortcuts for the |pseudocode| environment. (If you need to
+	specify options to |\setmonofont|, use |\setcodefont|.)
+\key{gantt}[\bool][false]
+	Load packages for the |ganttschedule| environment.
+\key{antonella}[\bool][false]
+	Use Dr.\ Antonella DiLillio's preferred styles (Courier for code)
+\key{solutions}[\bool][false]
+	Include |solution| environments in compiled document.
+\end{keys}
 
 \subsubsection{Configuration commands}%
 \label{sss:configcommands}
 
 \bps\ additionally provides a number of configuration commands for setting a
-single opption with similar interfaces as the \TeX\ macros \cs{author},
-\cs{title}, and \cs{date}.
-
-\begin{macro}{\duedate}\marg{date} sets the due date in full.\end{macro}
-\begin{macro}{\instructor}\marg{name} sets the instructor name.\end{macro}
-\begin{macro}{\course}\marg{name} sets the course name in full.\end{macro}
-\begin{macro}{\coursenumber}\marg{number} sets the course name by number; e.g.
-	|\coursenumber{21a}| gives a course of ``\cosi{21a}''.\end{macro}
-\begin{macro}{\assignment}\marg{name} sets the assignment name in full.\end{macro}
-\begin{macro}{\problemsetnumber}\marg{number} sets the assignment name by
-	number; e.g. |\problemsetnumber{3}| gives an assignment of ``Problem
-	Set 3''.\end{macro}
-
-\begin{macro}{\setcodefont}\oarg{fontspec options}\marg{font
-name}\AfterLastParam Sets the monospaced font to \meta{font name} and uses
-it for shortcuts in the \env{pseudocode} environment.
-
-\end{macro}
+single opption with similar interfaces as the \TeX\ macros |\author|,
+|\title|, and |\date|.
+
+\begin{desc}|\duedate{<date>}|\end{desc} Sets the due date in full.
+\begin{desc}|\instructor{<name>}|\end{desc} Sets the instructor name.
+\begin{desc}|\course{<name>}|\end{desc} Sets the course name in full.
+\begin{desc}|\coursenumber{<number>}|\end{desc} Sets the course name by
+	number; e.g. |\coursenumber{21a}| gives a course of ``\cosi{21a}''.
+\begin{desc}|\assignment{<name>}|\end{desc} Sets the assignment name in
+	full.
+\begin{desc}|\problemsetnumber{<number>}|\end{desc} Sets the assignment name
+	by number; e.g. |\problemsetnumber{3}| gives an assignment of
+	``Problem Set 3''.
+
+\begin{desc}
+|\setcodefont[<fontspec options>]{<fontspec font name>}|
+\end{desc}
+Sets the monospaced font to \meta{font name} and uses it for shortcuts in
+the |pseudocode| environment.
 
 \subsection{Practical usage}
 
@@ -162,8 +189,8 @@ files. For instance, \filename{cosi21a.cls} might read:
 }
 \author{Rebecca Turner}
 
-% get a prettier code font -- these can be pretty big so they're not loaded
-% by default
+% get a prettier code font -- these can be pretty big so they're not
+% loaded by default
 \setcodefont[
   Extension = .otf,
   UprightFont = *-Regular,
@@ -189,87 +216,107 @@ See section~\ref{sec:example} for a more complete example.
 
 \bps\ provides a number of commands for typesetting problems.
 
-\begin{macro}{problem}\oarg{options}\AfterLastParam Defines a problem. A
-problem is set 1~inch from the left margin (although this amount may be
-customized by modifying the \cs{problemindent} length) and begins a new
-page.
-
-\begin{Optionlist}
-title & A problem title, to be displayed after ``Problem'' and the problem's
-	number.\\
-number & A problem number; if given, the problem-number counter
-	will not advance. The number must be robust, because it goes inside
-	a \cs{section}. \\
-pagebreak & True/false (default: true). Add a pagebreak before the problem? \\
-label & Adds a custom label to the problem with \cs{label} that can be used
-	with \cs{ref} \\
-part & Indicates that this problem starts a new ``part'' of the assignment
-	\\
-partlabel & Adds a custom label to this part; see \option{label} \\
-\end{Optionlist}
-
-Vertical material is allowed in a~\env{problem}.
-\end{macro}
-
-\begin{macro}{solution}
+\begin{desc}
+|\begin{problem}[<options>]...\end{problem}|
+\end{desc}
+Defines a problem. A problem is set 1~inch from the left margin (although
+this amount may be customized by modifying the |\problemindent| length) and
+begins a new page. |<options>| may include:
+\begin{keys}
+\key{title}[\m{problem title}]
+	Displayed after ``Problem'' and the problem's number.
+\key{number}[\m{problem number}]
+	If given, the problem-number counter will not advance. The number
+	must be robust, because it goes inside a |\section|.
+\key{pagebreak}[\bool][true]
+	Add a pagebreak before the problem?
+\key{label}[\m{problem label}]
+	Adds a custom label to the problem with |\label| that can be used
+	with |\ref|. I recommend prefixing your problem labels with |p:| as
+	in |p:big-o-proofs|.
+\key{part}[\m{part name}]
+	Indicates that this problem starts a new ``part'' of the assignment;
+	actually calls |\part| under the hood.
+\key{partlabel}[\m{part label}]
+	Adds a custom label to this part in the same fashion as the
+	\option{label} key.
+\end{keys}
+
+Vertical material is allowed in a~|problem|.
+
+\begin{desc}
+|\begin{solution}...\end{solution}|
+\end{desc}
 
 Defines a solution for a problem; a solution prints in blue and is excluded
 from the compiled document entirely unless the \option{solutions} package
 option is given.
 
-In this way, the same \texttt{.tex} file can serve as both a postable assignment
-prompt and an answer key.
+In this way, the same \extension{tex} file can serve as both a postable
+assignment prompt and an answer key.
 
-\note{The style of solutions is customizable by redefining
-	\cs{solutionstyle}; it's defined to \cs{color}|{blue}| by default.}
+\begin{note}
+	The style of solutions is customizable by redefining
+	|\solutionstyle|; it's defined to |\color{blue}| by default.
+\end{note}
 
-\end{macro}
+\begin{desc}
+|\subproblem[<problem description>]|
+\end{desc}
+Prints a sub-problem, i.e.\ a |\subsection|. It doesn't do very much at the
+moment.
 
-\begin{macro}{\subproblem}\oarg{description}\AfterLastParam Prints a sub-problem, i.e.\ a
-\cs{subsection}. It doesn't do very much at the moment.
-\end{macro}
+\begin{desc}
+|\Th[<column spec>]{<header text>}|
+\end{desc}
 
-\begin{macro}{\Th}\oarg{colspec}\marg{header}\AfterLastParam Prints a table-header in bold.
-By default, the header is left-aligned, but arbitrary alignments can be
-specified with \meta{colspec}. \cs{Th} is backed by \cs{multicolumn}.
-\end{macro}
+Typesets a table header in bold-face. |<column spec>| defaults to |l|.
+Useful for when a column is wrapped in a math environment.
 
-\begin{macro}{pseudocode}\oarg{keywords}\AfterLastParam Prints
-pseudocode.\footnote{Designed for \cosi{21a} as taught by Dr.\ Antonella
-DiLillo}
+\begin{desc}
+|\begin{pseudocode}[<keywords>]...\end{pseudocode}|
+\end{desc}
+Prints pseudocode.\footnote{Designed for \cosi{21a} as taught by Dr.\
+Antonella DiLillo}
 
 Several ``shortcuts,'' which replace a source-code sequence like
 \texttt{->} with a symbol like $\rightarrow$, are shown in
 table~\ref{tab:pseudocode}.
 
-These shortcuts display in \cs{pseudocodesymbolfont} (default:
-\cs{ttfamily}), which may be redefined if you prefer something else. The
-easiest way to change \cs{pseudocodesymbolfont} is with \cs{setcodefont}. If
+These shortcuts display in |\pseudocodesymbolfont| (default:
+|\ttfamily|), which may be redefined if you prefer something else. The
+easiest way to change |\pseudocodesymbolfont| is with |\setcodefont|. If
 you use the \option{antonella} option with \fontspecok, \bps\ will load
 \ctan{lm-math} and display the symbols seen in table~\ref{tab:pseudocode},
-which look significantly better with Courier than \textsc{stix}' symbols.
+which look significantly better with Courier than \ctan{stix}' symbols.
 
 \begin{table}[h]
 	\centering
-	\caption{Shortcuts provided by the \env{pseudocode} environment}
+	\caption{Shortcuts provided by the \texttt{pseudocode}
+	environment}%
 	\label{tab:pseudocode}
-	\begin{tabular}{>{\ttfamily}lll}
-	\Th{Input} & \Th{Display} & \Th{Codepoint} \\
-	<-         & ←            & U+2190 \\
-	->         & →            & U+2192 \\
-	(/)        & $\emptyset$  & U+2205 \\
-	inf        & $\infty$     & U+221E \\
-	!=         & $\ne$        & U+2260 \\
-	>=         & $\ge$        & U+2265 \\
-	<=         & $\le$        & U+2264 \\
+	\begin{tabular}{lll}
+	\Th{Input}    & \Th{Display}  & \Th{Codepoint} \\
+	\ttfamily <-  & $\leftarrow$  & U+2190 \\
+	\ttfamily ->  & $\rightarrow$ & U+2192 \\
+	\ttfamily (/) & $\emptyset$   & U+2205 \\
+	\ttfamily inf & $\infty$      & U+221E \\
+	\ttfamily !=  & $\ne$         & U+2260 \\
+	\ttfamily >=  & $\ge$         & U+2265 \\
+	\ttfamily <=  & $\le$         & U+2264 \\
 	\end{tabular}
 \end{table}
 
-\todo{Improve the font selection mechanism; maybe provide a command for each
-	symbol?}
-\note{If your \TeX\ engine doesn't support \textsc{utf}-8 input, the
-	shortcuts might appear totally blank or garbled. Good luck! It will surely
-	work with \fontspecok.}
+\begin{todo}
+	Improve the font selection mechanism; maybe provide a command for
+	each symbol?
+\end{todo}
+
+\begin{todo}
+	If your \TeX\ engine doesn't support \textsc{utf}-8 input, the
+	shortcuts might appear totally blank or garbled. Good luck! It will
+	surely work with \fontspecok.
+\end{todo}
 
 \begin{latexcode}
 % the optional [Bar] makes [Bar] bold like the other keywords
@@ -290,17 +337,18 @@ Bar(a, n)
     return b
 \end{pseudocode}
 \end{latexcode}
-\end{macro}
 
-\begin{macro}{assembly}\oarg{extra options}\AfterLastParam typesets assembly
-code.\footnote{Designed for \cosi{131a} as taught by Dr.\ Liuba Shrira}
-Several considerations are taken into account; most notably, line numbers
-are printed as \texttt{x + n}, where $n$ starts at 0 and counts by 4; the
-line number actually indicates the instruction's location in memory as an
-offset from the program start. Additionally, all valid instructions are
-treated as keywords and styled appropriately.
+\begin{desc}
+|\begin{assembly}[<listings options>]...\end{assembly}|
+\end{desc}
+Typesets assembly code.\footnote{Designed for \cosi{131a} as taught by Dr.\
+Liuba Shrira} Several considerations are taken into account; most notably,
+line numbers are printed as \texttt{x + n}, where $n$ starts at 0 and counts
+by 4; the line number actually indicates the instruction's location in
+memory as an offset from the program start. Additionally, all valid
+instructions are treated as keywords and styled appropriately.
 
-Any extra options are passed directly to the \ctan{listings} package.
+|<listings options>| is passed directly to the \ctan{listings} package.
 
 \begin{latexcode}
 \begin{assembly}
@@ -319,44 +367,63 @@ OUTER:  BLT   R3, R2, INNER  ; while j < i goto inner
         HALT
 \end{assembly}
 \end{latexcode}
-\end{macro}
 
-\begin{macro}{java}\oarg{extra options}\AfterLastParam Tragically-common
-shorthand environment for a listing of Java code.
+\begin{desc}
+|\begin{java}[<listings options>]...\end{java}|
+\end{desc}
+Tragically-common shorthand environment for a listing of Java code.
 
-Any extra options are passed directly to the \ctan{listings} package.
-\end{macro}
+|<listings options>| is passed directly to the \ctan{listings} package.
 
-\begin{macro}{scheme}\oarg{extra options}\AfterLastParam Shorthand
-environment for a listing of Scheme code, useful for \cosi{121b}. Requires
-the \option{scheme} package option to be loaded.
+\begin{desc}
+|\begin{scheme}[<listings options>]...\end{scheme}|
+\end{desc}
+Shorthand environment for a listing of Scheme code, useful for \cosi{121b}.
+Requires the \option{scheme} package option to be loaded.
 
-Any extra options are passed directly to the \ctan{listings} package.
-\end{macro}
+|<listings options>| is passed directly to the \ctan{listings} package.
 
-\begin{macro}{ganttschedule}\marg{total cell count}\oarg{title}\AfterLastParam
+\begin{desc}
+|\begin{ganttschedule}[<total cell count>]...\end{ganttschedule}|
+\end{desc}
 An environment for drawing Gantt charts indicating process scheduling. The
 mandatory argument indicates how small the grid should be; \texttt{19}
 subdivides the line into 19 cells.
 
-To use the \env{ganttschedule} environment, make sure to use the
+To use the |ganttschedule| environment, make sure to use the
 \option{gantt} package option.
 
-Within a \env{ganttschedule}, use the \cs{burst} command to indicate an
+Within a |ganttschedule|, use the |\burst| command to indicate an
 active process (i.e.\ a process burst).
 
-\begin{macro}{\burst}\marg{pid}\marg{burst length}\AfterLastParam
-Draw a burst for process \marg{pid} of time length \meta{burst length}.
-\end{macro}
+\begin{note}
+	The charts |ganttschedule| draws aren't actually really proper Gantt
+	charts, which can indicate parallel activities; however, that's what
+	Liuba calls them, so that's what they're called here.
+\end{note}
+
+\begin{desc}
+|\pid{<pid>}{<burst length>}|
+\end{desc}
+Draw a burst for process |<pid>| of time length |<burst length>|.
+
+\begin{latexcode}
+\begin{ganttschedule}{19}
+	\burst{2}{1}
+	\burst{4}{1}
+	\burst{3}{2}
+	\burst{5}{5}
+	\burst{1}{10}
+\end{ganttschedule}
+\end{latexcode}
 
-\note{These aren't really Gantt charts, but that's what Dr.\ Shrira calls
-	them, so that's what they're called here.}
-\cprotect\note{Because \env{ganttschedule} relies on \ctan{tikz}, \ctan{fp},
-	and \ctan{calc}, it can add significantly to document compile times. If
-	you intend to use the \env{ganttschedule} environment, make sure to use
+\begin{note}
+	Because |ganttschedule| relies on \ctan{tikz}, \ctan{fp}, and
+	\ctan{calc}, it can add significantly to document compile times. If
+	you intend to use the |ganttschedule| environment, make sure to use
 	the \option{gantt} class option or set \option{gantt} in
-	\cs{problemsetsetup}. If you fail to include the \option{gantt} option,
-	you will see an error message:
+	|\problemsetsetup|. If you fail to include the \option{gantt}
+	option, you will see an error message:
 
 \begin{latexcode}
 ! Package brandeis-problemset Error: ganttschedule enviornment not loaded in preamble.
@@ -364,47 +431,37 @@ Draw a burst for process \marg{pid} of time length \meta{burst length}.
 See the brandeis-problemset package documentation for explanation.
 Type  H <return>  for immediate help.
 l.4 \burst
-          {1}{1}
+	{1}{1}
 ? H
 Did you mean to use the 'gantt' option for the brandeis-problemset document class?
 
 \end{latexcode}
-}
-
-\begin{latexcode}
-\begin{ganttschedule}{19}
-	\burst{2}{1}
-	\burst{4}{1}
-	\burst{3}{2}
-	\burst{5}{5}
-	\burst{1}{10}
-\end{ganttschedule}
-\end{latexcode}
-\end{macro}
+\end{note}
 
 \subsection{General formatting commands}
 
-\begin{macro}{\ac}\marg{acronym}\AfterLastParam
-Typesets an acronym. The \meta{acronym} should be lowercase (e.g.\
-\cs{ac}|{cpu}| rather than \cs{ac}|{CPU}|). Currently, \cs{ac} simply
-delegates to \cs{textsc}. In the future, I'd like to support a bit of
-letterspacing; ``for abbreviations and acronyms in the midst of normal text,
-use spaced small caps.''\footnote{\textit{The Elements of Typographic Style} by
-Robert Bringhurst, 2nd.\ ed, \S\ 3.2.2}
-\end{macro}
-
-\begin{macro}{\Sc}\marg{text}\AfterLastParam
-An abbreviation for \cs{textsc}\end{macro}
-\begin{macro}{\Rm}\marg{text}\AfterLastParam
-An abbreviation for \cs{textrm}\end{macro}
-\begin{macro}{\Up}\marg{text}\AfterLastParam
-An abbreviation for \cs{textup}\end{macro}
-\begin{macro}{\Bf}\marg{text}\AfterLastParam
-An abbreviation for \cs{textbf}\end{macro}
-\begin{macro}{\It}\marg{text}\AfterLastParam
-An abbreviation for \cs{textit}\end{macro}
-\begin{macro}{\Tt}\marg{text}\AfterLastParam
-An abbreviation for \cs{texttt}\end{macro}
+\begin{desc}
+|\ac{<acronym>}|
+\end{desc}
+Typesets an acronym. The |<acronym>| should be lowercase (e.g.\ |\ac{cpu}|
+rather than |\ac{CPU}|). Currently, |\ac| simply delegates to |\textsc|. In
+the future, I'd like to support a bit of letterspacing; ``for abbreviations
+and acronyms in the midst of normal text, use spaced small
+caps.''\footnote{\textit{The Elements of Typographic Style} by Robert
+Bringhurst, 2nd.\ ed, \S\ 3.2.2}
+
+\begin{desc}|\Sc{<text>}|\end{desc}
+An abbreviation for |\textsc|.
+\begin{desc}|\Rm{<text>}|\end{desc}
+An abbreviation for |\textrm|.
+\begin{desc}|\Up{<text>}|\end{desc}
+An abbreviation for |\textup|.
+\begin{desc}|\Bf{<text>}|\end{desc}
+An abbreviation for |\textbf|.
+\begin{desc}|\It{<text>}|\end{desc}
+An abbreviation for |\textit|.
+\begin{desc}|\Tt{<text>}|\end{desc}
+An abbreviation for |\texttt|.
 
 \section{Example}\label{sec:example}
 
@@ -484,52 +541,64 @@ $\Rm{Foo}(a, n)$ computes $a^n$, and will run in $O(n)$ time always.
 \end{latexcode}
 
 \begin{changelog}[author=Rebecca Turner]
+\begin{version}[v=0.4.2, date=2019-01-19]
+\added
+	\item |author| and |date| keys added to |\problemsetsetup| to
+	simplify class-wide configuration.
+\fixed
+	\item Fixed definitions for |\duedate|, |\instructor|, etc.\ to
+	avoid spurious errors due to undefined commands.
+\changed
+	\item Translated documentation to the new \ctan{ltxguidex} document
+	class for added beauty.
+	\item Re-licensed \bps\ to the \textsc{lppl} v1.3c for easy transfer of
+	maintenence in the future.
+\end{version}
+
 \shortversion{v=0.4.1, date=2019-01-03,
-	changes={Updated \env{scheme} environment to properly recognize all
+	changes={Updated |scheme| environment to properly recognize all
 	primitive functions, added syntax coloring to all code.}}
 
-\begin{version}[v=0.4.0]
+\begin{version}[v=0.4.0, date=2018-12-20]
 \added
-	\item \env{solution} environment and \option{solutions} class
+	\item |solution| environment and \option{solutions} class
 		option.
-	\item \env{scheme} shorthand environment and \option{scheme} class
+	\item |scheme| shorthand environment and \option{scheme} class
 		option.
 \fixed
 	\item Boolean class options being overwritten by keys defined for
-		\cs{problemsetsetup}.
+		|\problemsetsetup|.
 	\item Title-formatting errors
 \removed
 	\item Assignment- and course-specific class options
 		\option{duedate}, \option{assignment}, \option{instructor},
 		and \option{course}. These settings should be configured
-		with either \cs{problemsetsetup} or their specific commands.
-		(\cs{duedate}, \cs{instructor}, etc.).
+		with either |\problemsetsetup| or their specific commands.
+		(|\duedate|, |\instructor|, etc.).
 \end{version}
 
 \begin{version}[v=0.3.0, date=2018-10-24]
 \added
-	\item changelog.
-	\item support for \cs{part}s and referencing problems.
-	\item options to \env{problem} environment: \option{part},
+	\item This changelog.
+	\item Support for |\part|s and referencing problems.
+	\item Options to |problem| environment: \option{part},
 		\option{label}, and \option{partlabel}.
-	\item \cs{maketitle} (contrast with \cs{maketitlepage}).
+	\item |\maketitle| (contrast with |\maketitlepage|).
 \end{version}
 
 \begin{version}[v=0.2.0, date=2018-10-20]
 \changed
 	\item Class renamed to from \ltxclass{problemset} to \bps.
 \added
-	\item license header.
-	\item \env{ganttschedule} environment.
-	\item keywords to pseudocode environment: \texttt{and}, \texttt{or},
-		\texttt{nil}, and \texttt{len}.
-	\item \cs{ac} command for acronyms.
-	\item package example.
+	\item A license header.
+	\item |ganttschedule| environment.
+	\item Additional keywords for |pseudocode| environment:
+		\texttt{and}, \texttt{or}, \texttt{nil}, and \texttt{len}.
+	\item |\ac| command for acronyms.
+	\item An example document.
 \end{version}
 
 \shortversion{v=0.1.0, date=2018-10-19,
 	changes=Initial beta as \ltxclass{problemset}.}
 \end{changelog}
-
-\pagebreak\PrintIndex\listoftables
 \end{document}
diff --git a/Master/texmf-dist/doc/latex/brandeis-problemset/example.pdf b/Master/texmf-dist/doc/latex/brandeis-problemset/example.pdf
index f6c4d17ada0..4825e51aaac 100644
--- a/Master/texmf-dist/doc/latex/brandeis-problemset/example.pdf
+++ b/Master/texmf-dist/doc/latex/brandeis-problemset/example.pdf