DOCSP-41659: small typo fix (#3332)

## Pull Request Info

Jira ticket: https://jira.mongodb.org/browse/DOCSP-41659

- [Counters -
Node.js](https://preview-mongodbosharafmdb.gatsbyjs.io/realm/DOCSP-41659-nodejs-counters-typo/sdk/node/model-data/data-types/counters/):
fixed a small typo

### Reminder Checklist

Before merging your PR, make sure to check a few things.

- [N/A] Did you tag pages appropriately?
  - genre
  - programming_language
  - meta.keywords
  - meta.description
- [x] Describe your PR's changes in the Release Notes section
- [N/A] Create a Jira ticket for related docs-realm work, if any

### Release Notes

- **Node.js SDK**
- Model Data/Data Types/Counters: Fix typos on the Node.js SDK Counters
page.

### Review Guidelines


[REVIEWING.md](https://github.com/mongodb/docs-app-services/blob/master/REVIEWING.md)

Author: osharaf-mdb

source/sdk/node/model-data/data-types/counters.txt

@@ -29,7 +29,7 @@ the you can use as a logical counter when working with synchronized databases. T
 you would store a counter value and manually read, increment, and set it. However, if multiple clients
 attempt to update the counter, it could result in an inaccurate underlying value across clients.
 
-Consider a scenario where a REalm object hsa a ``count`` property of type ``int``. Devices A
+Consider a scenario where a Realm object has a ``count`` property of type ``int``. Devices A
 and B both read the value as ``0``, then increment the count by adding ``1`` to the read value.
 Instead of reflecting both devices' increments and converging to ``2``, the underlying value is
 only ``1``.