diff --git a/docs/docs/CMDB/models/BGP.md b/docs/docs/CMDB/models/BGP.md
index a0e4355..a8b5b6b 100644
--- a/docs/docs/CMDB/models/BGP.md
+++ b/docs/docs/CMDB/models/BGP.md
@@ -54,7 +54,8 @@ The main idea is to have a `BGPSession` linked to two `DeviceBGPSession` to avoi
 
 ```yaml
 BGPSession:
-    status: boolean
+    state: string choice
+    monitoring_state: string choice
     peer_a: cmdb.DeviceBGPSession
     peer_b: cmdb.DeviceBGPSession
     password: string
@@ -65,6 +66,7 @@ BGPSession:
 ```yaml
 DeviceBGPSession:
     device: dcim.Device
+    enabled: boolean
     description: string
     local_address: netbox.ipam.IPAddress
     remote_asn: cmdb.ASN
diff --git a/docs/docs/CMDB/models/Routing-Policies.md b/docs/docs/CMDB/models/Routing-Policies.md
index b7816b8..f3df831 100644
--- a/docs/docs/CMDB/models/Routing-Policies.md
+++ b/docs/docs/CMDB/models/Routing-Policies.md
@@ -28,14 +28,14 @@ erDiagram
 PrefixList:
     name: string
     device: dcim.Device
-    ip_version: string choices
+    ip_version: string choice
 ```
 
 ```yaml
 PrefixListTerm:
     prefix_list: cmdb.PrefixList
     sequence: integer
-    decision: string choices
+    decision: string choice
     prefix: IPNetwork
     le: integer
     ge: integer
@@ -55,7 +55,7 @@ BGPCommunityList:
 BGPCommunityListTerm:
     bgp_community_list: cmdb.BGPCommunityList
     sequence: integer
-    decision: string choices
+    decision: string choice
     community: string
 ```
 
@@ -73,7 +73,7 @@ RoutePolicyTerm:
     route_policy: cmdb.RoutePolicy
     description: string
     sequence: integer
-    decision: string choices
+    decision: string choice
 
     # match
     from_bgp_community: string
diff --git a/docs/docs/index.md b/docs/docs/index.md
index 224b6dd..61d544b 100644
--- a/docs/docs/index.md
+++ b/docs/docs/index.md
@@ -60,7 +60,7 @@ For instance, we represent the BGP session itself with two joined tables describ
 `DeviceBGPSession` <==> `BGPSession` <==> `DeviceBGPSession`
 
 * `DeviceBGPSession` contains the `local-as` but not the `peer-as`, avoiding data duplication. The `peer-as` being the `local-as` of the other neighbor.
-* `BGPSession` contains all information peers have in common, like status (`in production`, `maintenance` etc...) or `MD5 password`.
+* `BGPSession` contains all information peers have in common, like state (`in production`, `maintenance` etc...) or `MD5 password`.
 
 ### Data Aggregation API