Update with trademarks (#141)

* Update _index.md with trademark

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

* Update scverse_bw_logo.svg (#143)

* remove second trademark

* Update _index.md

* Update _index.md

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

Author: melonora

content/about/_index.md

@@ -2,7 +2,7 @@
 title = "About scverse"
 +++
 
-scverse is a consortium of foundational tools for analysis of omics data in life sciences. It has been founded to ensure the long-term maintenance of these core tools.
+scverse® is a consortium of foundational tools for analysis of omics data in life sciences. It has been founded to ensure the long-term maintenance of these core tools.
 
 Check out our [introductory blog post](/blog/hello-world) and [mission statement](/about/mission) for more details.
 

content/about/mission/_index.md

@@ -5,7 +5,7 @@ title = "Mission statement"
 
 ## Goals
 
-We want to make analysis tools for omics data in the life sciences as accessible as possible. This means:
+We as scverse® want to make analysis tools for omics data in the life sciences as accessible as possible. This means:
 
 * Interoperability -- we focus on developing open, standardized, and efficient file formats to encourage data sharing and re-use.
 * Diversity -- we believe in removing barriers to participation in research, including economic factors and institutional culture. Our tools will have the most impact if they are developed by and for a diverse community.

content/about/roles/_index.md

@@ -4,7 +4,7 @@ title = "Roles and Decisions"
 
 ## Roles and Responsibilities
 
-The purpose of this document is to formalize the governance process used by the `scverse` project, to clarify how decisions are made and how the various groups within our community interact.
+The purpose of this document is to formalize the governance process used by the `scverse®` project, to clarify how decisions are made and how the various groups within our community interact.
 
 As a whole, we are a consensus-based community project.
 However, any subproject within the scverse can have its own governance system as long as they do not conflict with the rules set out here.
@@ -121,4 +121,4 @@ Core members are expected to distinguish between fundamental objections to a pro
 If no option can be found without objections, the decision is escalated to the SC, which will itself use consensus seeking to come to a resolution.
 In the unlikely event that there is still a deadlock, the proposal will move forward if it has the support of a simple majority of the SC.
 
-If an objection is raised on a lazy consensus, the proposer can appeal to the community and core developers and the change can be approved or rejected by escalating to the SC.
+If an objection is raised on a lazy consensus, the proposer can appeal to the community and core developers and the change can be approved or rejected by escalating to the SC.