Follow new convention (StarkNet -> Starknet) (software-mansion#764)

* non breaking StarkNet -> Starknet

* StarkNet -> Starknet in contracts

* starknet -> Starknet

* error messages changed! starknet -> Starknet

* fix the guide

* fix `core` docs files

* fix api docs

* fix migration guide

Author: war-in

docs/account_creation.rst

@@ -2,7 +2,7 @@ Account creation
 ================
 
 
-An account is needed to start interacting with StarkNet.
+An account is needed to start interacting with Starknet.
 If you don't have one there are a few ways of creating one programmatically:
 
  - using DeployAccount transaction
@@ -20,7 +20,7 @@ Deploying an account with DeployAccount transaction requires the following:
  - computing an address based on the account's secrets
  - prefunding an address with the fee tokens (e.g. using the token bridge)
  - creating and signing a DeployAccount transaction with generated secrets
- - sending the transaction to StarkNet
+ - sending the transaction to Starknet
 
 Here is step by step example:
 

docs/api/messages.rst

@@ -1,13 +1,13 @@
-StarkNet <> Ethereum Messaging
+Starknet <> Ethereum Messaging
 ==============================
 
 .. warning::
-    StarkNet <> Ethereum Messaging module is deprecated. If you are using it,
-    please contact us on our StarkNet discord channel: starknet-py.
+    Starknet <> Ethereum Messaging module is deprecated. If you are using it,
+    please contact us on our Starknet discord channel: starknet-py.
 
 .. _Messaging:
 
-Module containing utilities to operate on StarkNet ->  Ethereum and Ethereum -> StarkNet messages
+Module containing utilities to operate on Starknet ->  Ethereum and Ethereum -> Starknet messages
 
 .. py:module:: starknet_py.net.l1.messages
 

docs/api/signer.rst

@@ -15,7 +15,7 @@ BaseSigner interface
 BaseSigner default implementation
 ---------------------------------
 
-By default, StarkNet.py uses ``StarkCurveSigner`` which works with OpenZeppelin's account contract.
+By default, starknet.py uses ``StarkCurveSigner`` which works with OpenZeppelin's account contract.
 
 .. py:module:: starknet_py.net.signer.stark_curve_signer
 

docs/conf.py

@@ -21,7 +21,7 @@
 
 # -- Project information -----------------------------------------------------
 
-project = "Starknet.py"
+project = "starknet.py"
 copyright = "2023, Software Mansion"
 author = "Software Mansion"
 
@@ -78,8 +78,8 @@
 pygments_dark_style = "dracula"
 
 html_favicon = "_static/favicon.png"
-html_title = "StarkNet.py Documentation"
-html_short_title = "StarkNet.py"
+html_title = "starknet.py Documentation"
+html_short_title = "starknet.py"
 html_permalinks_icon = "#"
 
 html_theme_options = {

docs/development.rst

@@ -120,7 +120,7 @@ Rules to follow when writing a code:
 Release checklist
 -------------------
 
-Perform these actions before releasing a new StarkNet.py version
+Perform these actions before releasing a new starknet.py version
 
 1. Bump package version in ``pyproject.toml``
 2. Re-lock using ``poetry lock --no-update``

docs/guide/account_and_client.rst

@@ -17,14 +17,14 @@ Here is an example:
 FullNodeClient usage
 --------------------
 
-Use a :ref:`FullNodeClient` to interact with services providing `starknet rpc interface <https://github.com/starkware-libs/starknet-specs/blob/606c21e06be92ea1543fd0134b7f98df622c2fbf/api/starknet_api_openrpc.json>`_
-like `Pathfinder Full Node <https://github.com/eqlabs/pathfinder>`_ or starknet-devnet. StarkNet.py provides uniform interface for
+Use a :ref:`FullNodeClient` to interact with services providing `Starknet rpc interface <https://github.com/starkware-libs/starknet-specs/blob/606c21e06be92ea1543fd0134b7f98df622c2fbf/api/starknet_api_openrpc.json>`_
+like `Pathfinder Full Node <https://github.com/eqlabs/pathfinder>`_ or starknet-devnet. starknet.py provides uniform interface for
 both gateway and full node client - usage is exactly the same as gateway client minus some optional
 parameters.
 
-Using own full node allows for querying StarkNet with better performance.
+Using own full node allows for querying Starknet with better performance.
 Since gateway will be deprecated at some point in the future, having ``FullNodeClient`` with interface uniform with that of ``GatewayClient``
-will allow for simple migration for StarkNet.py users.
+will allow for simple migration for starknet.py users.
 
 .. codesnippet:: ../../starknet_py/tests/e2e/docs/guide/test_full_node_client.py
     :language: python
@@ -43,7 +43,7 @@ You can use :class:`starknet_py.net.client_errors.ClientError` to catch errors f
 Custom nonce logic
 ------------------
 
-By default, :ref:`Account` calls StarkNet for nonce every time a new transaction is signed or executed.
+By default, :ref:`Account` calls Starknet for nonce every time a new transaction is signed or executed.
 This is okay for most users, but in case your applications needs to pre-sign multiple transactions
 for execution, deals with high amount of transactions or just needs to support different nonce
 logic, it is possible to so with :ref:`Account`. Simply overwrite the

docs/guide/deploying_contracts.rst

@@ -23,7 +23,7 @@ Here's an example how to use it.
 Simple declare and deploy
 -------------------------
 
-The simplest way of declaring and deploying contracts on the StarkNet is to use the :ref:`Contract` class.
+The simplest way of declaring and deploying contracts on the Starknet is to use the :ref:`Contract` class.
 Under the hood, this flow sends :meth:`Declare` transaction and then sends :meth:`InvokeFunction`
 through Universal Deployment Contract (UDC) to deploy a contract.
 

docs/guide/ethereum_communication.rst

@@ -1,20 +1,20 @@
-StarkNet <> Ethereum communication
+Starknet <> Ethereum communication
 ==================================
 
 .. warning::
-    StarkNet <> Ethereum Messaging module is deprecated. If you are using it,
-    please contact us on our StarkNet discord channel: starknet-py.
+    Starknet <> Ethereum Messaging module is deprecated. If you are using it,
+    please contact us on our Starknet discord channel: starknet-py.
 
-To retrieve the StarkNet -> Ethereum or Ethereum -> StarkNet message count, you need to provide some data that you used to create that message.
+To retrieve the Starknet -> Ethereum or Ethereum -> Starknet message count, you need to provide some data that you used to create that message.
 Then after creating the message's representation, you can query its current count.
 
-You can find out more about StarkNet <> Ethereum messaging here: https://starknet.io/documentation/l1-l2-messaging/
+You can find out more about Starknet <> Ethereum messaging here: https://starknet.io/documentation/l1-l2-messaging/
 
 Full API description :ref:`here<Messaging>`.
 
 
 
-Ethereum -> StarkNet messages
+Ethereum -> Starknet messages
 #############################
 
 The message's count is an `int`, representing the number of unconsumed messages on L2 with that exact content.
@@ -26,7 +26,7 @@ Since the `nonce`'s value will always be unique for each message, this value is
     :dedent: 4
 
 
-StarkNet -> Ethereum messages
+Starknet -> Ethereum messages
 #############################
 
 As in previous section, you can provide L1 message content, and then fetch the queued message count.

docs/guide/resolving_proxy_contracts.rst

@@ -4,9 +4,9 @@ Resolving proxy contracts
 .. note::
     If you know the abi of the contract, **always prefer** creating Contract directly from constructor.
 
-    :meth:`Contract.from_address <starknet_py.contract.Contract.from_address>` must perform some calls to StarkNet to get an abi of the contract.
+    :meth:`Contract.from_address <starknet_py.contract.Contract.from_address>` must perform some calls to Starknet to get an abi of the contract.
 
-Resolving proxies is a powerful feature of Starknet.py. If your contract is a proxy to some implementation, you can use
+Resolving proxies is a powerful feature of starknet.py. If your contract is a proxy to some implementation, you can use
 high-level :meth:`Contract.from_address <starknet_py.contract.Contract.from_address>` method to get a contract instance.
 
 :meth:`Contract.from_address <starknet_py.contract.Contract.from_address>` works with contracts which are not proxies, so it is the most universal method of getting
@@ -22,9 +22,9 @@ a contract not knowing the abi.
 ProxyChecks
 -----------
 
-Since the Proxy contracts on StarkNet can have different implementations, as every user can define their custom implementation, there is no single way of checking if some contract is a Proxy contract.
+Since the Proxy contracts on Starknet can have different implementations, as every user can define their custom implementation, there is no single way of checking if some contract is a Proxy contract.
 
-There are two main ways of proxying a contract on StarkNet:
+There are two main ways of proxying a contract on Starknet:
  - forward the calls using ``library_call`` and ``class_hash`` of proxied contract
  - forward the calls using ``delegate_call`` and ``address`` of proxied contract
 

docs/guide/serialization.rst

@@ -4,7 +4,7 @@ Serialization
 Data serialization
 -------------------
 
-Starknet.py **serializes** python values to Cairo values and **deserializes** Cairo values to python values.
+starknet.py **serializes** python values to Cairo values and **deserializes** Cairo values to python values.
 
 .. attention::
     Serializing short strings to felts has been deprecated. Please use `starknet_py.cairo.felt.encode_shortstring` to