Google Git
Sign in
fuchsia/third_party/github.com/project-chip/zap/refs/heads/upstream/support_upper_camel^!/.
commit
c2ab4f6a5475576d6a9fa5c252c443b676a49407
[log]
author
Andrei Litvin <andreilitvin@google.com>
Thu Apr 03 16:21:49 2025 -0400
committer
Andrei Litvin <andreilitvin@google.com>
Thu Apr 03 16:21:49 2025 -0400
tree
a3e96f78455e8699b480d9b91ffe3b53d63d2d03
parent
6a9a9da989e19faabf72ac7f5a54a2dc9852881a [diff]
Undo some formatting

diff --git a/docs/sdk-integration.md b/docs/sdk-integration.md
index 555c0c9..46af240 100644
--- a/docs/sdk-integration.md
+++ b/docs/sdk-integration.md

@@ -12,7 +12,7 @@
 
 To gain these abilities, the SDK should provide data to zap. The data required is:
 
-- **ZCL metafiles**: these are the metafiles that provide information about the ZCL specification to zap tool. Examples of this (and currently supported) are Silicon Labs XML ZCL metadata or the Zigbee official XML format of the ZCL metafiles. Examples of these metafiles are available from the Zigbee website (<http://zigbee.org>).
+- **ZCL metafiles**: these are the metafiles that provide information about the ZCL specification to zap tool. Examples of this (and currently supported) are Silicon Labs XML ZCL metadata or the Zigbee official XML format of the ZCL metafiles. Examples of these metafiles are available from the Zigbee website (http://zigbee.org).
 
   The ZAP project itself provides examples as well, see the `zcl-builtin/` directory. These are used internally for unit testing, but they are also packaged with the application as examples. They can be a good starting point for SDK developers, but ultimately it's the responsibility of SDK developers to provide the accurate XML packages for their SDK, and let ZAP know where they can be loaded from on the local hard drive.