DOCSP-55700-remove-atlas-from-concept-pages (#16519)

## Description

Remove Atlas callouts from high-level pages where they don't add much
value.

## Staged

-
[Documents](https://deploy-preview-16519--mongodb-manual.netlify.app/docs/upcoming/core/document/)
- [Server Selection
Algorithm](https://deploy-preview-16519--mongodb-manual.netlify.app/docs/upcoming/core/read-preference-mechanics/)
- [Specify JSON
Schema](https://deploy-preview-16519--mongodb-manual.netlify.app/docs/upcoming/core/schema-validation/specify-json-schema/)
-
[Transactions](https://deploy-preview-16519--mongodb-manual.netlify.app/docs/upcoming/core/transactions/)
- [Geospatial
Queries](https://deploy-preview-16519--mongodb-manual.netlify.app/docs/upcoming/geospatial-queries/)
- [Database
References](https://deploy-preview-16519--mongodb-manual.netlify.app/docs/upcoming/reference/database-references/)
- [Limits and
Thresholds](https://deploy-preview-16519--mongodb-manual.netlify.app/docs/upcoming/reference/limits/?atlas-provider=aws&atlas-class=general)
- [Expire Data using
TTL](https://deploy-preview-16519--mongodb-manual.netlify.app/docs/upcoming/tutorial/expire-data/)

## JIRA

https://jira.mongodb.org/browse/DOCSP-55700

Author: jeff-allen-mongo

content/manual/upcoming/source/core/document.txt

@@ -26,14 +26,6 @@ types than JSON. For the BSON spec, see `bsonspec.org
 
 .. include:: /images/crud-annotated-document.rst
 
-Compatibility
--------------
-
-MongoDB stores records as documents for deployments hosted in the
-following environments:
-
-.. include:: /includes/fact-environments.rst
-
 .. _document-structure:
 
 Document Structure

content/manual/upcoming/source/core/read-preference-mechanics.txt

@@ -22,11 +22,6 @@ replica set member to use or, when connected to multiple
 
 Server selection occurs once per operation.
 
-The information on this page applies to deployments hosted in the 
-following environments:
-
-.. include:: /includes/fact-environments.rst
-
 .. note::
 
    .. include:: /includes/extracts/transactions-read-pref.rst

content/manual/upcoming/source/core/schema-validation/specify-json-schema.txt

@@ -32,13 +32,6 @@ JSON Schema is a vocabulary that allows you to annotate and validate
 JSON documents. You can use JSON schema to specify validation rules for
 your fields in a human-readable format.
 
-Compatibility
--------------
-
-.. |operator-method| replace:: JSON schema validation
-
-.. include:: /includes/fact-compatibility.rst
-
 Context
 -------
 

content/manual/upcoming/source/core/transactions.txt

@@ -36,11 +36,6 @@ distributed transactions. With distributed transactions,
 transactions can be used across multiple operations, collections,
 databases, documents, and shards.
 
-The information on this page applies to deployments hosted in the 
-following environments:
-
-.. include:: /includes/fact-environments.rst
-
 Transactions API
 ----------------
 

content/manual/upcoming/source/geospatial-queries.txt

@@ -24,20 +24,7 @@ Geospatial Queries
    :class: singlecol
 
 MongoDB supports query operations on geospatial data. This section
-introduces MongoDB's geospatial features. 
-
-.. |page-topic| replace:: run geospatial queries
-
-Compatibility
--------------
-
-.. |operator-method| replace:: geospatial queries
-
-.. include:: /includes/fact-compatibility.rst
-
-For deployments hosted in {+atlas+}, you can run geospatial 
-queries in the UI by using the query :guilabel:`Filter` bar or aggregation 
-builder. To learn more, see :ref:`geospatial-queries-atlas`.
+introduces MongoDB's geospatial features.
 
 .. _geo-overview-location-data:
 

content/manual/upcoming/source/reference/database-references.txt

@@ -39,11 +39,6 @@ or databases.
 This page outlines alternative procedures that predate the
 :pipeline:`$lookup` and :pipeline:`$graphLookup` pipeline stages.
 
-You can create a database reference for deployments hosted in the
-following environments:
-
-.. include:: /includes/fact-environments.rst
-
 MongoDB applications use one of two methods to relate documents:
 
 - :ref:`Manual references <document-references>` save the

content/manual/upcoming/source/reference/limits.txt

@@ -22,11 +22,10 @@ MongoDB Limits and Thresholds
    :depth: 1
    :class: singlecol
 
-This document provides a collection of hard and soft limitations of
-the MongoDB system. The limitations on this page apply to deployments
-hosted in all of the following environments unless specified otherwise:
-
-.. include:: /includes/fact-environments.rst
+This document provides a collection of hard and soft limitations of the
+MongoDB system. The limitations on this page apply to deployments hosted
+in Atlas and self-hosted MongoDB deployments, unless specified
+otherwise.
 
 {+atlas+} Limitations
 ------------------------------

content/manual/upcoming/source/tutorial/expire-data.txt

@@ -25,11 +25,6 @@ store data in MongoDB and have the :binary:`~bin.mongod` automatically
 remove data after a specified number of seconds or at a specific clock
 time.
 
-You can expire data for deployments hosted in the following
-environments:
-
-.. include:: /includes/fact-environments.rst
-
 Data expiration is useful for some classes of information, including
 machine generated event data, logs, and session information that only
 need to persist for a limited period of time.