API & Library References -> API References

README.md

@@ -27,7 +27,7 @@
   - [Repositories](#repositories)
     - [Add Links to a Repository](#add-links-to-a-repository)
     - [Release Versions](#release-versions)
-  - [API & Library References](#api--library-references)
+  - [API References](#api-references)
     - [Swagger specs](#swagger-specs)
     - [TypeDoc specs](#typedoc-specs)
 - [Development](#development)
@@ -49,7 +49,7 @@ The documentation is split in multiple sections whose content lives in this repo
 - **Core concepts**: high-level explanation of concepts, assumptions, and components
 - **Setup**: getting started for various stakeholders and use cases
 - **Tutorials**: detailed tutorials
-- **API & Library References**: docs for the Aquarius & Brizo REST APIs, and docs for various Squid libraries
+- **API References**: docs for the Aquarius & Brizo REST APIs, and docs for various Squid libraries
 
 Those sections are defined in the [`/data/sections.yml`](data/sections.yml) file.
 
@@ -184,7 +184,7 @@ The GitHub link is automatically added for every repository and will always be d
 
 The displayed version number is based on the tag name of the latest release for a given repository. That means only GitHub releases will trigger a version number update, creating a new Git tag alone is not sufficient.
 
-### API & Library References
+### API References
 
 You can add more Markdown documents under `/content/references/`, link to them from the [`/data/sidebars/references.yml`](./data/sidebars/references.yml), and they will appear just like in all the other sections.
 

data/sections.yml

@@ -13,7 +13,7 @@
   link: /tutorials/introduction/
   color: orange
 
-- title: API & Library References
+- title: API References
   description: Get the references for REST APIs and library methods for all relevant components.
   link: /references/introduction/
   color: green